![]() | |||||||||||||
Messages in this thread |
Ulrich Drepper <drepper@redhat.com> writes: > Eric W. Biederman wrote: > > > >> sym = dlsym (RTLD_DEFAULT, "the_symbol_name") > > [...] > > > > > For the momen the only finished port is x86, so we should be able > > to do that, it would make the kernel patch a little bigger though. > > Last time I saw that conversation I thought you didn't like symbols in > > the vdso for syscalls because it slowed things down. > > I don't want to use this in glibc for every syscall. But for your > random application in need of a syscall it's fine. The question that had come up earlier was fast path syscalls like gettimeofday. > And there is one more thing: the above code is actually not what should > be used. The symbol able entries should be position independent. So > one will have to compute the final address (which will be fun for archs > with function descriptors). I'll have to see how randomization is > actually implemented. The __kernel_vsyscall symbol is probably not > changed, so we need an out-of-band mechanisms to report the load address > to the userlevel code. We currently have AT_SYSINFO_EHDR and AT_SYSINFO which should report the basic location information. As a first draft we should be able to use the standard ELF mechanisms for this. It is not like PIC shared libraries were new. Or is there some specific problem you are thinking of with respect to randomization? Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:03 [from the cache] ©2003-2008 | |||||||||||||