From: Catalin Marinas <catalin.marinas@arm.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.31-rc6, BTRFS] potential memory leaks...
Date: Fri, 14 Aug 2009 17:35:07 +0100 [thread overview]
Message-ID: <tnxab228ibo.fsf@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <6278d2220908140803g554ab931o58672a1b4c11e245@mail.gmail.com> (Daniel J. Blueman's message of "Fri\, 14 Aug 2009 16\:03\:04 +0100")
Daniel J Blueman <daniel.blueman@gmail.com> wrote:
> There is good chance that the BTRFS kmemleak reports using 2.6.31-rc6
> [1] are false-positives, due to the overwriting of the static pointers
> [2]. Does this ring true with anyone else?
If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
disappear?
The static pointers are scanned by kmemleak, unless they are in the
.data.init section (which is removed anyway).
--
Catalin
next prev parent reply other threads:[~2009-08-14 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 15:03 [2.6.31-rc6, BTRFS] potential memory leaks Daniel J Blueman
2009-08-14 15:05 ` Chris Mason
2009-08-14 16:35 ` Catalin Marinas [this message]
2009-08-16 12:55 ` Daniel J Blueman
2009-08-16 21:38 ` Catalin Marinas
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=tnxab228ibo.fsf@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.