[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0804261213200.28624@mtl.rackplans.net>
Date: Sat, 26 Apr 2008 12:15:11 -0400 (EDT)
From: Gerhard Mack <gmack@...erfire.net>
To: Jiri Kosina <jkosina@...e.cz>
cc: linux-kernel@...r.kernel.org
Subject: Re: [2.6.25] compat VDSO option not disabling
I havn't enabled compat VDSO at the kernel command line or otherwise.
Something broke with this option.
Gerhard
On Fri, 25 Apr 2008, Jiri Kosina wrote:
> Date: Fri, 25 Apr 2008 16:33:48 +0200 (CEST)
> From: Jiri Kosina <jkosina@...e.cz>
> To: Gerhard Mack <gmack@...erfire.net>
> Cc: linux-kernel@...r.kernel.org
> Subject: Re: [2.6.25] compat VDSO option not disabling
>
> On Thu, 24 Apr 2008, Gerhard Mack wrote:
>
> > On my laptop I disabled the compat vdso option but it is till being
> > mapped.. Any ideas?
>
> The changelog of the commit below explains that.
>
> commit 1dbf527c51c6c20c19869c8125cb5b87c3d09506
> Author: Jeremy Fitzhardinge <jeremy@...p.org>
> Date: Wed May 2 19:27:12 2007 +0200
>
> [PATCH] i386: Make COMPAT_VDSO runtime selectable.
>
> Now that relocation of the VDSO for COMPAT_VDSO users is done at
> runtime rather than compile time, it is possible to enable/disable
> compat mode at runtime.
>
> This patch allows you to enable COMPAT_VDSO mode with "vdso=2" on the
> kernel command line, or via sysctl. (Switching on a running system
> shouldn't be done lightly; any process which was relying on the compat
> VDSO will be upset if it goes away.)
>
> The COMPAT_VDSO config option still exists, but if enabled it just
> makes vdso_enabled default to VDSO_COMPAT.
>
>
--
Gerhard Mack
gmack@...erfire.net
<>< As a computer I find your faith in technology amusing.
--
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