| 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.1507141304430.28065@east.gentwo.org> Date: Tue, 14 Jul 2015 13:11:42 -0500 (CDT) From: Christoph Lameter <cl@...ux.com> To: Konstantin Khlebnikov <khlebnikov@...dex-team.ru> cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] mm/slub: disable merging after enabling debug in runtime On Tue, 14 Jul 2015, Konstantin Khlebnikov wrote: > Enabling debug in runtime breaks creation of new kmem caches: > they have incompatible flags thus cannot be merged but unique > names are taken by existing caches. What breaks? Caches may already have been merged and thus the question is what to do about a cache that has multiple aliases if a runtime option is requested. The solution that slub implements is to only allow a limited number of debug operations to be enabled. Those then will appear to affect all aliases of course. Creating additional caches later may create additional aliasing which will then restrict what options can be changed. Other operations are also restricted depending on the number of objects stored in a cache. A cache with zero objects can be easily reconfigured. If there are objects then modifications that impact object size are not allowed anymore. -- 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