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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 20 Jul 2011 09:30:36 +0100
From:	Catalin Marinas <>
To:	Nick Bowler <>
Cc:	"" <>,
	"" <>
Subject: Re: kmemleak fails to report detected leaks after allocation

On Tue, Jul 19, 2011 at 10:14:38PM +0100, Nick Bowler wrote:
> I just ran into a somewhat amusing issue with kmemleak.  After running
> for a while (10 days), and detecting about 100 "suspected memory leaks",
> kmemleak ultimately reported:
>   kmemleak: Cannot allocate a kmemleak_object structure
>   kmemleak: Automatic memory scanning thread ended
>   kmemleak: Kernel memory leak detector disabled
> OK, so something failed and kmemleak apparently can't recover from
> this.  However, at this point, it appears that kmemleak has *also*
> lost the ability to report the earlier leaks that it actually
> detected.
>   cat: /sys/kernel/debug/kmemleak: Device or resource busy
> It seems to me that kmemleak shouldn't lose the ability to report leaks
> that it already detected after it disables itself due to an issue that
> was potentially caused by the very leaks that it managed to detect
> (unlikely in this instance, but still...).

Very good point, I haven't thought of this. I'll try to improve this


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists