vDSO

vDSO (virtual dynamic shared object) is a kernel mechanism for exporting a carefully selected set of <a href="/facts/Kernel_space/0yIzMY8t">kernel space</a> routines to <a href="/facts/User_space/0yIzMY8t">user space</a> applications so that applications can call these kernel space routines in-process, without incurring the performance penalty of a <a href="/facts/Mode_switch_(computing)/N0oJQ6CC">mode switch</a> from <a href="/facts/User_mode/0yIzMY8t">user mode</a> to <a href="/facts/Kernel_mode/27y4kjHs">kernel mode</a> that is inherent when calling these same kernel space routines by means of the <a href="/facts/System_call/NW44AFJr">system call</a> interface.
vDSO uses standard mechanisms for <a href="/facts/Linker_(computing)/pn1hztYe">linking</a> and <a href="/facts/Loader_(computing)/eIK4f2xB">loading</a> i.e. standard <a href="/facts/Executable_and_Linkable_Format/ro2CYqso">Executable and Linkable Format</a> (ELF) format. vDSO is a memory area allocated in user space which exposes some kernel functionalities. vDSO is <a href="/facts/Dynamic_allocation/vthLkUpz">dynamically allocated</a>, offers improved safety through <a href="/facts/Address_space_layout_randomization/K6lMxWTr">address space layout randomization</a>, and supports more than four system calls. Some <a href="/facts/C_standard_libraries/qdG1nW2c">C standard libraries</a>, like <a href="/facts/Glibc/AL6IYDkA">glibc</a>, may provide vDSO links so that if the kernel does not have vDSO support, a traditional <a href="/facts/Syscall/NW44AFJr">syscall</a> is made. vDSO helps to reduce the calling overhead on simple kernel routines, and it also can work as a way to select the best system-call method on some <a href="/facts/Computer_architectures/tHtwxgR2">computer architectures</a> such as <a href="/facts/IA-32/7yTv1aHH">IA-32</a>. An advantage over other methods is that such exported routines can provide proper <a href="/facts/DWARF/dRRIGNKS">DWARF</a> (Debug With Attributed Record Format) debugging information. Implementation generally implies hooks in the dynamic linker to find the vDSOs.
vDSO was developed to offer the vsyscall features while overcoming its limitations: a small amount of <a href="/facts/Static_memory_allocation/dYIs2E5p">statically allocated</a> memory, which allows only four system calls, and the same addresses <a href="/facts/Application_binary_interface/wc6pmKKb">application binary interface</a> (ABI) in each process, which compromises security. This security issue has been mitigated by <a href="/facts/Sigreturn-oriented_programming/cyHULXv9">emulating a virtual system call</a>, but the emulation introduces additional latency.
<a href="/facts/Glibc/AL6IYDkA">glibc</a> has support for getrandom() vDSO.

vDSO open-in-new

vDSO