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: Sat, 21 Jul 2007 03:18:09 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "Bret Towe" <magnade@...il.com> Cc: "Ulrich Kunitz" <kune@...ne-taler.de>, linux-kernel@...r.kernel.org, Jan Kratochvil <honza@...os.cz>, Jiri Kosina <jkosina@...e.cz>, Roland McGrath <roland@...hat.com>, Jakub Jelinek <jakub@...hat.com> Subject: Re: Is PIE randomization breaking klibc binaries? On Fri, 20 Jul 2007 23:02:12 -0700 "Bret Towe" <magnade@...il.com> wrote: > On 7/20/07, Ulrich Kunitz <kune@...ne-taler.de> wrote: > > Since this week new linux-2.6/master kernels don't work with my > > initial ram disks. The sleep binary runs repeatingly into > > segmentation faults until the Busybox shell starts. My system is a > > x86-64 with Kubuntu Feisty Fawn. > > > > By bisecting I found out that the PIE randomization patch (commit 60bfba7e) > > appears to cause the segmentation faults. > > > > Digging further into the issue I found out, that the sleep binary > > on the initial ramdisk is a klibc binary. /usr/bin/file says it is > > statically linked and uses shared libraries. I have no clue about > > klibc, but the binaries seem to be statically linked, but load a > > shared library; probably at a fixed address. Other klibc binaries are also > > running into segmentation faults. Busybox is working, but it is > > statically linked and doesn't use a shared library. > > > > It looks like that the PIE randomization patch breaks klibc > > binaries on x86-64. > > > > -- > > Uli Kunitz > > - > > oh bugger I just spent a few hours bisecting to find this headache > only to find someone else had 8 hours ago... *sigh* > > anyhow also seeing seg faults here on a amd64 ubuntu system > reverting the PIE randomization patch made it go away (cc's added) I don't think we'll be fixing this in time for -rc1. I'll revert it. Thanks for the prompt and accurate reporting. - 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