https://bugzilla.suse.com/show_bug.cgi?id=1202385 https://bugzilla.suse.com/show_bug.cgi?id=1202385#c2 --- Comment #2 from Martin Li��ka <martin.liska@suse.com> --- (In reply to Jiri Slaby from comment #1)
(In reply to Martin Li��ka from comment #0)
Thus a suggested fix can be putting the vdso a separate kernel-source-userspace package or so.
It'd have to be in kernel-%{flavor}-vdso instead -- it's different for different flavors. In that case kernel-%{flavor}-vdso-debug* should be created automatically.
Ah, I see.
I think it's not that hard to do that on the kernel side. The questions is: do we also need "Require: kernel-%{flavor}-vdso" in kernel-%{flavor} to drag it automatically in?
I guess so ...
I.e. what tools read vdso.so if any at all?
Because dynamic linker loads it if I'm correct: $ ldd `which echo` linux-vdso.so.1 (0x00007ffff7fc1000) libc.so.6 => /lib64/libc.so.6 (0x00007ffff7c00000) /lib64/ld-linux-x86-64.so.2 (0x00007ffff7fc3000) -- You are receiving this mail because: You are on the CC list for the bug.