From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 60121] -next and -mm: kmemleak reports 6 leaks in ext4_mount paths
Date: Wed, 26 Jun 2013 05:32:33 +0000 (UTC) [thread overview]
Message-ID: <20130626053233.BF2DF11FECB@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-60121-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60121
--- Comment #1 from Dave Chinner <david@fromorbit.com> 2013-06-26 05:32:33 ---
On Tue, Jun 25, 2013 at 06:25:04PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=60121
>
> Summary: -next and -mm: kmemleak reports 6 leaks in ext4_mount
> paths
> Product: File System
> Version: 2.5
> Kernel Version: v3.10-rc6-684-g9dcc58c
> Platform: All
> OS/Version: Linux
> Tree: -mm
> Status: NEW
> Severity: normal
> Priority: P1
> Component: ext4
> AssignedTo: fs_ext4@kernel-bugs.osdl.org
> ReportedBy: jmesmon@gmail.com
> Regression: Yes
>
>
> Created an attachment (id=106021)
--> (https://bugzilla.kernel.org/attachment.cgi?id=106021)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=106021)
> .config
>
> In next-20130624, next-20130625 and mmotm (v3.10-rc6-684-g9dcc58c), kmemleak
> complains about some ext4_mount related allocations.
Has nothing to do with ext4, and fixes are already on the way to -mm
and -next. Thread here:
http://marc.info/?l=linux-fsdevel&m=137154854120579&w=2
Cheers,
Dave.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-06-26 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 18:25 [Bug 60121] New: -next and -mm: kmemleak reports 6 leaks in ext4_mount paths bugzilla-daemon
2013-06-26 5:32 ` Dave Chinner
2013-06-26 5:32 ` bugzilla-daemon [this message]
2013-11-13 19:45 ` [Bug 60121] " bugzilla-daemon
2013-11-13 19:46 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130626053233.BF2DF11FECB@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).