| 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
| ||
|
Message-ID: <alpine.DEB.2.11.1509081013190.25292@east.gentwo.org> Date: Tue, 8 Sep 2015 10:15:00 -0500 (CDT) From: Christoph Lameter <cl@...ux.com> To: Nikolay Borisov <kernel@...p.com> cc: "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>, Marian Marinov <mm@...com>, SiteGround Operations <operations@...eground.com> Subject: Re: Kernel 4.1.6 Panic due to slab corruption On Tue, 8 Sep 2015, Nikolay Borisov wrote: > > You have read https://www.kernel.org/doc/Documentation/vm/slub.txt? > > I've read that I'm also following the merge/nomerge thread on the DM > mailing list. I guess my understanding is wrong in that if multiple slab > caches are merged, then it's enough to just instrument the cache to > which they are being merge in order to have them all instrumented? I > guess that's not the case, so even though slab caches might be merge > they are still somehow considered different entities in the kernel? Enabling debugging on bootup disables merging. If you switch debug options later then its possible to affect all aliases caches. But then these option changes are only allowed to be used in such a way as to not affect the object layout. You can switch on sanity checks and double free checks I believe but nothing else. -- 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