Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO

2007-01-24 Thread Paul Mundt
On Wed, Jan 17, 2007 at 01:03:34AM -0800, Roland McGrath wrote: > > i think your patches #1...#7 are must-haves for v2.6.20, while #8-#11 > > could be delayed to v2.6.21? > > Indeed 1-7 are fixes while 8-11 are only cleanups not changing behavior. > Here's an update for the SH bits when the 8-11

Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO

2007-01-17 Thread Roland McGrath
> i think your patches #1...#7 are must-haves for v2.6.20, while #8-#11 > could be delayed to v2.6.21? Indeed 1-7 are fixes while 8-11 are only cleanups not changing behavior. Thanks, Roland - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [E

Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO

2007-01-17 Thread Ingo Molnar
* Roland McGrath <[EMAIL PROTECTED]> wrote: > I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's > there, it should work properly. Currently it's quite haphazard: both > real vma and fixmap are mapped, both are put in the two different AT_* > slots, sysenter returns to the

Re: [PATCH 1/11] Fix CONFIG_COMPAT_VDSO

2007-01-15 Thread Al Boldi
Roland McGrath wrote: > > I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. > But if it's there, it should work properly. Currently > it's quite haphazard: both real vma and fixmap are > mapped, both are put in the two different AT_* slots, > sysenter returns to the vma address rather than

[PATCH 1/11] Fix CONFIG_COMPAT_VDSO

2007-01-13 Thread Roland McGrath
I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely. But if it's there, it should work properly. Currently it's quite haphazard: both real vma and fixmap are mapped, both are put in the two different AT_* slots, sysenter returns to the vma address rather than the fixmap address, and core dum