| 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: <1215411800.8970.91.camel@pasglop> Date: Mon, 07 Jul 2008 16:23:20 +1000 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: Roland McGrath <roland@...hat.com> Cc: Nathan Lynch <ntl@...ox.com>, linuxppc-dev@...abs.org, Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] elf loader support for auxvec base platform string On Sun, 2008-07-06 at 23:18 -0700, Roland McGrath wrote: > > Using dsocaps gives you the best of both worlds. You can freely choose > new strings in the kernel without the ld.so code having to know about > them (which is not true of AT_PLATFORM, but may be true of how you are > thinking about "strings are nice"). You do have to map all the > possibilities that a single kernel build can produce into distinct bits. > But, there are 32 unallocated bits to start with. Moreover, those bit > assignments are not part of any permanent ABI like bits in AT_* values. > They just have to match up between this kernel build and the ld.conf.d > file installed along with it--kernel hackers and kernel packagers have > to coordinate, not kernel hackers and userland hackers. I'm not sure... if ld.conf.d isn't parse of the kernel source tree then it -will- end in tears... Ben. -- 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