| 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
| ||
|
Date: Fri, 17 Jul 2015 10:09:49 -0500 (CDT) From: Christoph Lameter <cl@...ux.com> To: Konstantin Khlebnikov <koct9i@...il.com> cc: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>, "linux-mm@...ck.org" <linux-mm@...ck.org>, Andrew Morton <akpm@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/2] mm/slub: disable merging after enabling debug in runtime On Fri, 17 Jul 2015, Konstantin Khlebnikov wrote: > > Hrm.... Bad. Maybe drop the checks for the debug options that can be > > configured when merging slabs? They do not influence the object layout > > per definition. > > I don't understand that. Debug options do changes in object layout. Only some debug options change the object layout and those are alrady forbidden for caches with objects. > Since they add significant performance overhead and cannot be undone in runtime > it's unlikely that anyone who uses them don't care about merging after that. Those that do not affect the object layout can be undone. > Also I don't see how merging could affect debugging in positive way > (except debugging bugs in merging logic itself). The problem here is that debugging is switched on for slabs that are already merged right? -- 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