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-next>] [day] [month] [year] [list]
Date:	Tue, 4 Oct 2011 07:31:47 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: kmemleak and SLAB

Hi,

When I try to use kmemleak with the SLAB allocator set I receive this
message when booting 3.1-rc8:

[   28.480569] kmemleak: Cannot allocate a kmemleak_object structure
[   28.480593] kmemleak: Kernel memory leak detector disabled
[   34.428037] CPA self-test:
[   34.435881]  4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[   34.447669]  4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[   34.458402]  4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[   34.458407] ok.
[   38.754032] wlan0: no IPv6 routers present
[   67.666048] kmemleak: Automatic memory scanning thread ended

All is fine when using SLUB. On another run I also got an error about an
ODEBUG oom so I wonder if this is indicative of another problem...

-- 
Sitsofe | http://sucs.org/~sits/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ