From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932297AbWETJey (ORCPT ); Sat, 20 May 2006 05:34:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932303AbWETJey (ORCPT ); Sat, 20 May 2006 05:34:54 -0400 Received: from mailout1.vmware.com ([65.113.40.130]:17676 "EHLO mailout1.vmware.com") by vger.kernel.org with ESMTP id S932297AbWETJey (ORCPT ); Sat, 20 May 2006 05:34:54 -0400 Message-ID: <446EE1C2.7060400@vmware.com> Date: Sat, 20 May 2006 02:30:42 -0700 From: Zachary Amsden User-Agent: Thunderbird 1.5.0.2 (X11/20060420) MIME-Version: 1.0 To: Andrew Morton Cc: Ingo Molnar , torvalds@osdl.org, rusty@rustcorp.com.au, linux-kernel@vger.kernel.org, virtualization@lists.osdl.org, kraxel@suse.de Subject: Re: [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled References: <1147759423.5492.102.camel@localhost.localdomain> <20060516064723.GA14121@elte.hu> <1147852189.1749.28.camel@localhost.localdomain> <20060519174303.5fd17d12.akpm@osdl.org> <20060520010303.GA17858@elte.hu> <20060519181125.5c8e109e.akpm@osdl.org> <20060520085351.GA28716@elte.hu> <20060520022650.46b048f8.akpm@osdl.org> In-Reply-To: <20060520022650.46b048f8.akpm@osdl.org> Content-Type: multipart/mixed; boundary="------------060906030303020707040108" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This is a multi-part message in MIME format. --------------060906030303020707040108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andrew Morton wrote: > vmm:/home/akpm# echo 1 > /proc/sys/vm/vdso_enabled > vmm:/home/akpm# > vmm:/home/akpm> ls -l > zsh: segmentation fault ls -l > > >> That could tell us whether >> it's an init bug or a glibc bug. >> > > It tells us neither. This could be a new kernel bug which only certain old > userspace setups are known to trigger. Until we know exactly why this is > occurring, we don't know where the bug is. > > And once we've worked that thing out, and if we determine that the bug is > in userspace then we might be able to craft the patch in such a fashion > that the old userspace continues to work, which would be a win. > Please try my patch - sent earlier, but attached again. It will tell you with 100% confidence if the problem is with userspace expecting the vsyscall page to be at a particular address. --------------060906030303020707040108 Content-Type: text/plain; name="bogo-fixmap" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bogo-fixmap" 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 --------------060906030303020707040108--