обзор виртуального динамического общего объекта ELF (overview of the virtual ELF dynamic shared object)
Примечание (Note)
Source
When you compile the kernel, it will automatically compile and
link the vDSO code for you. You will frequently find it under
the architecture-specific directory:
find arch/$ARCH/ -name '*vdso*.so*' -o -name '*gate*.so*'
vDSO names
The name of the vDSO varies across architectures. It will often
show up in things like glibc's ldd(1) output. The exact name
should not matter to any code, so do not hardcode it.
user ABI vDSO name
─────────────────────────────
aarch64 linux-vdso.so.1
arm linux-vdso.so.1
ia64 linux-gate.so.1
mips linux-vdso.so.1
ppc/32 linux-vdso32.so.1
ppc/64 linux-vdso64.so.1
riscv linux-vdso.so.1
s390 linux-vdso32.so.1
s390x linux-vdso64.so.1
sh linux-gate.so.1
i386 linux-gate.so.1
x86-64 linux-vdso.so.1
x86/x32 linux-vdso.so.1
strace(1), seccomp(2), and the vDSO
When tracing systems calls with strace(1), symbols (system calls)
that are exported by the vDSO will not appear in the trace
output. Those system calls will likewise not be visible to
seccomp(2) filters.
