public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, virtualization@lists.osdl.org, kraxel@suse.de
Subject: Re: [PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch
Date: Fri, 19 May 2006 18:16:44 -0700	[thread overview]
Message-ID: <446E6DFC.5010808@vmware.com> (raw)
In-Reply-To: <20060519181125.5c8e109e.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Andrew Morton wrote:
> Ingo Molnar <mingo@elte.hu> wrote:
>   
>> * Andrew Morton <akpm@osdl.org> wrote:
>>
>>     
>>> Rusty Russell <rusty@rustcorp.com.au> 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.
>>>       
>> FC1 is like really ancient. I think there was a glibc bug that caused 
>> vsyscall related init hangs like that. To nevertheless let people run 
>> their old stuff there's a vdso=0 boot option in exec-shield.
>>
>>     
>
> Well that patch took a machine from working to non-working.  Pretty serious
> stuff.  We should get to the bottom of the problem so we can assess the
> risk and impact, no?

An easy test for culpability of kernel vs. init would be to back out all 
patches and recompile the kernel with vsyscall moved down by 4 megs.



[-- Attachment #2: bogo-fixmap --]
[-- Type: text/plain, Size: 512 bytes --]


Index: linux-2.6.17-rc/include/asm-i386/fixmap.h
===================================================================
--- linux-2.6.17-rc.orig/include/asm-i386/fixmap.h	2006-03-19 21:53:29.000000000 -0800
+++ linux-2.6.17-rc/include/asm-i386/fixmap.h	2006-05-19 18:16:00.000000000 -0700
@@ -20,7 +20,7 @@
  * Leave one empty page between vmalloc'ed areas and
  * the start of the fixmap.
  */
-#define __FIXADDR_TOP	0xfffff000
+#define __FIXADDR_TOP	0xffbff000
 
 #ifndef __ASSEMBLY__
 #include <linux/kernel.h>

  parent reply	other threads:[~2006-05-20  1:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  6:03 [PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch Rusty Russell
2006-05-16  6:47 ` Ingo Molnar
2006-05-16  8:16   ` Zachary Amsden
2006-05-16  8:40     ` Chris Wright
2006-05-16  8:59       ` Zachary Amsden
2006-05-17  7:49   ` Rusty Russell
2006-05-18  7:54     ` Ingo Molnar
2006-05-18  8:29       ` Gerd Hoffmann
2006-05-20  0:43     ` Andrew Morton
2006-05-20  1:03       ` Ingo Molnar
2006-05-20  1:11         ` Andrew Morton
2006-05-20  1:15           ` Linus Torvalds
2006-05-20  8:53             ` [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled Ingo Molnar
2006-05-20  9:26               ` Andrew Morton
2006-05-20  9:30                 ` Zachary Amsden
2006-05-20  9:43                   ` Zachary Amsden
2006-05-20  9:48                   ` Andrew Morton
2006-05-20 10:04                     ` Zachary Amsden
2006-05-21  4:38                       ` Rusty Russell
2006-05-21  9:35                         ` Rusty Russell
2006-05-21  9:52                           ` Andrew Morton
2006-05-21 10:41                           ` Ingo Molnar
2006-05-21 11:06                             ` Rusty Russell
2006-05-20  9:54                 ` Ingo Molnar
2006-05-20 10:16                 ` [patch] add print_fatal_signals support Ingo Molnar
2006-05-21 11:03                 ` [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled Ingo Molnar
2006-05-21 11:38                   ` Ingo Molnar
2006-05-21 12:33                     ` Andrew Morton
2006-05-21 14:10                 ` Arjan van de Ven
2006-05-22 14:32                   ` Alexey Kuznetsov
2006-05-20  1:16           ` Zachary Amsden [this message]
2006-05-20  1:49           ` [PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch Andi Kleen
2006-05-20  1:24       ` Arjan van de Ven
2006-05-22 16:29       ` Jakub Jelinek
2006-05-22 16:44         ` Zachary Amsden
2006-05-22 17:14           ` Andrew Morton
2006-05-22 17:27             ` Ingo Molnar
2006-05-22 17:46               ` Linus Torvalds
2006-05-22 19:09                 ` Ingo Molnar
2006-05-22 19:40                   ` Linus Torvalds
2006-05-22 19:14                 ` Adrian Bunk
2006-05-22 19:45                   ` Linus Torvalds
2006-05-22 17:53               ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446E6DFC.5010808@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@osdl.org \
    --cc=kraxel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@osdl.org \
    --cc=virtualization@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox