Jakub Jelinek wrote: > Prelink ATM doesn't take VDSO into account at all and surely it would > be best if it did not have to. For example if VDSO is randomized, userspace > has no control over its placement like it has for shared libraries > (if DSO base is NULL, kernel randomizes, if non-NULL (usually means > prelinked), then does not randomize unless the binary is PIE). Randomisation of vDSO and randomisation of PIE, or non-PIE objects which don't get mapped where you intended all break prelinking. In this regard vDSO is no different to any other library. I agree that any uses of randomisation tend to break prelinking, and so it's not reasonable to depend solely on prelinking. -- Jamie - 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/
References:
- [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchjohn stultz
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJamie Lokier
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJamie Lokier
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJamie Lokier
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJakub Jelinek
- Prev by Date: Re: [CRYPTO]: Miscompiling sha256.c by gcc 3.2.3 and arch pentium3,4
- Next by Date: Re: Encrypted Filesystem
- 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]