On Fri, May 19, 2006 at 05:43:03PM -0700, Andrew Morton wrote: > Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote: > > > > Name: Move vsyscall page out of fixmap into normal vma as per mmap > > This causes mysterious hangs when starting init. > > Distro is RH FC1, running SysVinit-2.85-5. > > dmesg, sysrq-T and .config are at > http://www.zip.com.au/~akpm/linux/patches/stuff/log-vmm - nothing leaps > out. > > This is the second time recently when a patch has caused this machine to > oddly hang in init. It's possible that there's a bug of some form in that > version of init that we'll need to know about and take care of in some > fashion. That's known bug in early glibcs short after adding vDSO support. The vDSO support has been added in May 2003 to CVS glibc (i.e. post glibc 2.3.2) and the problems have been fixed when they were discovered, in February 2004: http://sources.redhat.com/ml/libc-hacker/2004-02/msg00053.html http://sources.redhat.com/ml/libc-hacker/2004-02/msg00059.html I strongly believe we want randomized vDSOs, people are already abusing the fix mapped vDSO for attacks, and I think the unfortunate 10 months of broken glibc shouldn't stop that forever. Anyone using such glibc can still use vdso=0, or do that just once and upgrade to somewhat more recent glibc. Jakub
