| 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: <1206170695.2438.39.camel@entropy> Date: Sat, 22 Mar 2008 00:24:55 -0700 From: Nicholas Miell <nmiell@...cast.net> To: Andi Kleen <andi@...stfloor.org> Cc: Ulrich Drepper <drepper@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH prototype] [0/8] Predictive bitmaps for ELF executables On Sat, 2008-03-22 at 08:17 +0100, Andi Kleen wrote: > On Fri, Mar 21, 2008 at 09:36:51PM -0700, Ulrich Drepper wrote: > > On Fri, Mar 21, 2008 at 10:26 AM, Andi Kleen <andi@...stfloor.org> wrote: > > > Concrete suggestions please. > > > > I already spelled it out. Add a new program header entry, point it to > > a bit array large enough to cover all loadable segments. > > Ah that's easy, the program header is already supported in the kernel code > (PT_PRESENT_BITMAP) > > The additional SHDR is just there for easier testing/migration. > > > > It is not worth creating problems with this invalid extension just for > > You still didn't say why it was invalid. > > Anyways I disagree on the value of supporting old binaries. I believe > it is important. > > -Andi Why not stick the bitmap in an xattr? -- Nicholas Miell <nmiell@...cast.net> -- 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