linux-kernel - Re: [2.6.31-rc6, BTRFS] potential memory leaks...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <tnxab228ibo.fsf@pc1117.cambridge.arm.com>
Date:	Fri, 14 Aug 2009 17:35:07 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Daniel J Blueman <daniel.blueman@...il.com>
Cc:	Linux BTRFS <linux-btrfs@...r.kernel.org>,
	Chris Mason <chris.mason@...cle.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.31-rc6, BTRFS] potential memory leaks...

Daniel J Blueman <daniel.blueman@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/