On Fri, Feb 06, 2004 at 01:23:23AM -0800, Ulrich Drepper wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Andrea Arcangeli wrote: > > > I don't think I was arguing against it completely, exactly because I'm > > just saying it should be optional. > > And the result is that the current fast syscall handling on x86-64 is > completely unacceptable. If it's not change security enhancements are > not possible since the libc has to hardcode the address. by the same argument the 2.6 i386 vsyscall is not acceptable too since it has an hardcoded address too that is the same for all binary kernels that you ship, and furthmore it has the sysenter or int 0x80 hardcoded at a fixed address to jump into. In short either you claim the 2.6.2 i386 code as broken the way glibc calls into it, or x86-64 is perfectly fine too. so your claims makes very little sense to me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchAndrea Arcangeli
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchRik van Riel
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchAndrea Arcangeli
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Prev by Date: Re: 2.4.25-rc1: BUG: wrong zone alignment, it will crash
- Next by Date: Re: [Bugme-new] [Bug 2019] New: Bug from the mm subsystem involving X (fwd)
- Previous by thread: Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch
- Next by thread: Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch
- Indexes:[Main][Thread]