Changes in Makefile.vdsoinst

fc2f5f10 - s390/vdso: Create .build-id links for unstripped vdso files

Mon, 29 Apr 2024 15:02:53 +0000

s390/vdso: Create .build-id links for unstripped vdso filesCiting Andy Lutomirski from commit dda1e95cee38 ("x86/vdso: Create.build-id links for unstripped vdso files"):"With this change, doing 'make vdso_install' and telling gdb:set debug-file-directory /lib/modules/KVER/vdsowill enable vdso debugging with symbols. This is useful fortesting, but kernel RPM builds will probably want to manually deletethese symlinks or otherwise do something sensible when they stripthe vdso/*.so files."Fixes: 4bff8cb54502 ("s390: convert to GENERIC_VDSO")Signed-off-by: Jens Remus Signed-off-by: Alexander Gordeev List of files: /linux-6.15/scripts/Makefile.vdsoinst

1c369b6c - kbuild: simplify generic vdso installation code

Mon, 29 Apr 2024 15:07:54 +0000

kbuild: simplify generic vdso installation codeWith commit 4b0bf9a01270 ("riscv: compat_vdso: install compat_vdso.so.dbgto /lib/modules/*/vdso/") applied, all debug VDSO files are installed in$(MODLIB)/vdso/.Simplify the installation rule.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile.vdsoinst

c1a86271 - kbuild: fix build ID symlinks to installed debug VDSO files

Wed, 20 Dec 2023 08:18:33 +0000

kbuild: fix build ID symlinks to installed debug VDSO filesCommit 56769ba4b297 ("kbuild: unify vdso_install rules") accidentallydropped the '.debug' suffix from the build ID symlinks.Fixes: 56769ba4b297 ("kbuild: unify vdso_install rules")Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile.vdsoinst

56769ba4 - kbuild: unify vdso_install rules

Sat, 14 Oct 2023 10:54:35 +0000

kbuild: unify vdso_install rulesCurrently, there is no standard implementation for vdso_install,leading to various issues: 1. Code duplication Many architectures duplicate similar code just for copying files to the install destination. Some architectures (arm, sparc, x86) create build-id symlinks, introducing more code duplication. 2. Unintended updates of in-tree build artifacts The vdso_install rule depends on the vdso files to install. It may update in-tree build artifacts. This can be problematic, as explained in commit 19514fc665ff ("arm, kbuild: make "make install" not depend on vmlinux"). 3. Broken code in some architectures Makefile code is often copied from one architecture to another without proper adaptation. 'make vdso_install' for parisc does not work. 'make vdso_install' for s390 installs vdso64, but not vdso32.To address these problems, this commit introduces a generic vdso_installrule.Architectures that support vdso_install need to define vdso-install-yin arch/*/Makefile. vdso-install-y lists the files to install.For example, arch/x86/Makefile looks like this: vdso-install-$(CONFIG_X86_64) += arch/x86/entry/vdso/vdso64.so.dbg vdso-install-$(CONFIG_X86_X32_ABI) += arch/x86/entry/vdso/vdsox32.so.dbg vdso-install-$(CONFIG_X86_32) += arch/x86/entry/vdso/vdso32.so.dbg vdso-install-$(CONFIG_IA32_EMULATION) += arch/x86/entry/vdso/vdso32.so.dbgThese files will be installed to $(MODLIB)/vdso/ with the .dbg suffix,if exists, stripped away.vdso-install-y can optionally take the second field after the colonseparator. This is needed because some architectures install a vdsofile as a different base name.The following is a snippet from arch/arm64/Makefile. vdso-install-$(CONFIG_COMPAT_VDSO) += arch/arm64/kernel/vdso32/vdso.so.dbg:vdso32.soThis will rename vdso.so.dbg to vdso32.so during installation. If sucharchitectures change their implementation so that the base names match,this workaround will go away.Signed-off-by: Masahiro Yamada Acked-by: Sven Schnelle # s390Reviewed-by: Nicolas Schier Reviewed-by: Guo Ren Acked-by: Helge Deller # pariscAcked-by: Catalin Marinas Acked-by: Russell King (Oracle) List of files: /linux-6.15/scripts/Makefile.vdsoinst