linux-kernel - Re: kmemleak disabled itself in 2.6.36

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: <201010281513.26185.toralf.foerster@gmx.de>
Date:	Thu, 28 Oct 2010 15:13:25 +0200
From:	Toralf Förster <toralf.foerster@....de>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Subject: Re: kmemleak disabled itself in 2.6.36


Catalin Marinas wrote at 10:33:09
> On Wed, 2010-10-27 at 20:12 +0100, Toralf Förster wrote:
> > I'm unsure whether this happens due to a
> > $> sudo su -c "echo clear > /sys/kernel/debug/kmemleak"
> > or while regular scanning, but anyway seems not to be normal, or ?
> > 
> > 2010-10-27T20:42:21.697+02:00 n22 kernel: flush-254:0: page allocation
> > failure. order:0, mode:0x0
> 
> [...]
> 
> > 2010-10-27T20:42:21.699+02:00 n22 kernel: kmemleak: Cannot allocate a
> > kmemleak_object structure 2010-10-27T20:42:21.699+02:00 n22 kernel: Pid:
> > 15475, comm: flush-254:0 Not tainted 2.6.36 #2
> 
> [...]
> 
> > 2010-10-27T20:42:21.700+02:00 n22 kernel: kmemleak: Kernel memory leak
> > detector disabled
> 
> Are you running out of memory on your system? Kmemleak tried to allocate
> a structure but the slab allocator failed to get page. Kmemleak disables
> itself in such situations but the problem is somewhere else (not enough
> memory?).
> 
> Catalin

I don't think so - no big load to that system, no excessive compiler runs ...

-- 
MfG/Kind regards
Toralf Förster

pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

--
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/