Changes in Makefile

127b0e05 - vdso: Rename included Makefile

Tue, 04 Feb 2025 12:05:36 +0000

vdso: Rename included MakefileAs the Makefile is included into other Makefiles it can not be used todefine objects to be built from the current source directory.However the generic datastore will introduce such a local source file.Rename the included Makefile so it is clear how it is to be used and tomake room for a regular Makefile in lib/vdso/.Signed-off-by: Thomas Weißschuh Signed-off-by: Thomas Gleixner Link: https://lore.kernel.org/all/20250204-vdso-store-rng-v3-4-13a4669dfc8c@linutronix.de List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

48f64305 - arm64/vdso: Remove --hash-style=sysv

Thu, 18 Jul 2024 17:34:23 +0000

arm64/vdso: Remove --hash-style=sysvglibc added support for .gnu.hash in 2006 and .hash has been obsoletedfor more than one decade in many Linux distributions. Using--hash-style=sysv might imply unaddressed issues and confuse readers.Just drop the option and rely on the linker default, which is likely"both", or "gnu" when the distribution really wants to eliminate sysvhash overhead.Similar to commit 6b7e26547fad ("x86/vdso: Emit a GNU hash").Signed-off-by: Fangrui Song Link: https://lore.kernel.org/r/20240718173423.1574395-1-maskray@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

b957df3b - arch: use $(obj)/ instead of $(src)/ for preprocessed linker scripts

Sat, 27 Apr 2024 14:54:59 +0000

arch: use $(obj)/ instead of $(src)/ for preprocessed linker scriptsThese are generated files. Prefix them with $(obj)/ instead of $(src)/.Signed-off-by: Masahiro Yamada Acked-by: Helge Deller Reviewed-by: Nicolas Schier List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

c7767f5c - arm64: vdso32: Remove unused vdso32-offsets.h

Mon, 29 Jan 2024 15:47:48 +0000

arm64: vdso32: Remove unused vdso32-offsets.hCommit 2d071968a405 ("arm64: compat: Remove 32-bit sigreturn codefrom the vDSO") removed all VDSO_* symbols in the compat vDSO. As aresult, vdso32-offsets.h is now empty and therefore unused. Time toremove it.Signed-off-by: Kevin Brodsky Link: https://lore.kernel.org/r/20240129154748.1727759-1-kevin.brodsky@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

a099bec7 - arm64: vdso32: rename 32-bit debug vdso to vdso32.so.dbg

Fri, 17 Nov 2023 12:56:19 +0000

arm64: vdso32: rename 32-bit debug vdso to vdso32.so.dbg'make vdso_install' renames arch/arm64/kernel/vdso32/vdso.so.dbg tovdso32.so during installation, which allows 64-bit and 32-bit vdsofiles to be installed in the same directory.However, arm64 is the only architecture that requires this renaming.To simplify the vdso_install logic, rename the in-tree vdso file soits base name matches the installed file name.Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20231117125620.1058300-1-masahiroy@kernel.orgSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

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/arch/arm64/kernel/vdso32/Makefile

b5ec6fd2 - kbuild: Drop -Wdeclaration-after-statement

Fri, 09 Jun 2023 09:28:30 +0000

kbuild: Drop -Wdeclaration-after-statementWith the advent on scope-based resource management it comes reallytedious to abide by the contraints of -Wdeclaration-after-statement.It will still be recommeneded to place declarations at the start of ascope where possible, but it will no longer be enforced.Suggested-by: Linus Torvalds Signed-off-by: Peter Zijlstra (Intel) Link: https://lkml.kernel.org/r/CAHk-%3Dwi-RyoUhbChiVaJZoZXheAwnJ7OO%3DGxe85BkPAd93TwDA%40mail.gmail.com List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

aff69273 - vdso: Improve cmd_vdso_check to check all dynamic relocations

Fri, 10 Mar 2023 19:07:50 +0000

vdso: Improve cmd_vdso_check to check all dynamic relocationsThe actual intention is that no dynamic relocation exists in the VDSO. Forthis the VDSO build validates that the resulting .so file does not have anyrelocations which are specified via $(ARCH_REL_TYPE_ABS) per architecture,which is fragile as e.g. ARM64 lacks an entry for R_AARCH64_RELATIVE. Asideof that ARCH_REL_TYPE_ABS is a misnomer as it checks for relativerelocations too.However, some GNU ld ports produce unneeded R_*_NONE relocation entries. Ifa port fails to determine the exact .rel[a].dyn size, the trailing zerosbecome R_*_NONE relocations. E.g. ld's powerpc port recently fixedhttps://sourceware.org/bugzilla/show_bug.cgi?id=29540). R_*_NONE aregenerally a no-op in the dynamic loaders. So just ignore them.Remove the ARCH_REL_TYPE_ABS defines and just validate that the resulting.so file does not contain any R_* relocation entries except R_*_NONE.Signed-off-by: Fangrui Song Signed-off-by: Thomas Gleixner Tested-by: Vincenzo Frascino # for aarch64Reviewed-by: Christophe Leroy Reviewed-by: Vincenzo Frascino # for vDSO, aarch64Acked-by: Michael Ellerman (powerpc)Link: https://lore.kernel.org/r/20230310190750.3323802-1-maskray@google.com List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

e1789d7c - kbuild: upgrade the orphan section warning to an error if CONFIG_WERROR is set

Tue, 25 Oct 2022 07:30:23 +0000

kbuild: upgrade the orphan section warning to an error if CONFIG_WERROR is setAndrew Cooper suggested upgrading the orphan section warning to a hard linkerror. However Nathan Chancellor said outright turning the warning into anerror with no escape hatch might be too aggressive, as we have had thesewarnings triggered by new compiler generated sections, and suggested turningorphan sections into an error only if CONFIG_WERROR is set. Kees Cook echoedand emphasized that the mandate from Linus is that we should avoid breakingbuilds. It wrecks bisection, it causes problems across compiler versions, etc.Thus upgrade the orphan section warning to a hard link error only ifCONFIG_WERROR is set.Suggested-by: Andrew Cooper Suggested-by: Nathan Chancellor Signed-off-by: Xin Li Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor Signed-off-by: Kees Cook Link: https://lore.kernel.org/r/20221025073023.16137-2-xin3.li@intel.com List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

9d4775b3 - arm64: vdso32: enable orphan handling for VDSO

Tue, 10 May 2022 09:58:34 +0000

arm64: vdso32: enable orphan handling for VDSOLike vmlinux, enable orphan-handling for the compat VDSO32. This can catchsubtle errors that might arise from unexpected sections being included.Signed-off-by: Joey Gouly Cc: Catalin Marinas Cc: Will Deacon Cc: Masahiro Yamada Cc: Vincenzo Frascino Cc: Kees Cook Reviewed-by: Kees Cook Reviewed-by: Vincenzo Frascino Link: https://lore.kernel.org/r/20220510095834.32394-5-joey.gouly@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

205f3991 - arm64: vdso: fix makefile dependency on vdso.so

Tue, 10 May 2022 10:27:21 +0000

arm64: vdso: fix makefile dependency on vdso.soThere is currently no dependency for vdso*-wrap.S on vdso*.so, which means thatyou can get a build that uses a stale vdso*-wrap.o.In commit a5b8ca97fbf8, the file that includes the vdso.so was moved and renamedfrom arch/arm64/kernel/vdso/vdso.S to arch/arm64/kernel/vdso-wrap.S, when thishappened the Makefile was not updated to force the dependcy on vdso.so.Fixes: a5b8ca97fbf8 ("arm64: do not descend to vdso directories twice")Signed-off-by: Joey Gouly Cc: Masahiro Yamada Cc: Vincenzo Frascino Cc: Catalin Marinas Cc: Will Deacon Link: https://lore.kernel.org/r/20220510102721.50811-1-joey.gouly@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

e8c07082 - Kbuild: move to -std=gnu11

Tue, 08 Mar 2022 21:56:14 +0000

Kbuild: move to -std=gnu11During a patch discussion, Linus brought up the option of changingthe C standard version from gnu89 to gnu99, which allows using variabledeclaration inside of a for() loop. While the C99, C11 and later standardsintroduce many other features, most of these are already available ingnu89 as GNU extensions as well.An earlier attempt to do this when gcc-5 started defaulting to-std=gnu11 failed because at the time that caused warnings aboutdesignated initializers with older compilers. Now that gcc-5.1 isthe minimum compiler version used for building kernels, that is nolonger a concern. Similarly, the behavior of 'inline' functions changesbetween gnu89 using gnu_inline behavior and gnu11 using standard c99+behavior, but this was taken care of by defining 'inline' to include__attribute__((gnu_inline)) in order to allow building with clang awhile ago.Nathan Chancellor reported a new -Wdeclaration-after-statementwarning that appears in a system header on arm, this still needs aworkaround.The differences between gnu99, gnu11, gnu1x and gnu17 are fairlyminimal and mainly impact warnings at the -Wpedantic level that thekernel never enables. Between these, gnu11 is the newest versionthat is supported by all supported compiler versions, though it isonly the default on gcc-5, while all other supported versions ofgcc or clang default to gnu1x/gnu17.Link: https://lore.kernel.org/lkml/CAHk-=wiyCH7xeHcmiFJ-YgXUy2Jaj7pnkdKpcovt8fYbVFW3TA@mail.gmail.com/Link: https://github.com/ClangBuiltLinux/linux/issues/1603Suggested-by: Linus Torvalds Acked-by: Marco Elver Acked-by: Jani Nikula Acked-by: David Sterba Tested-by: Sedat Dilek Reviewed-by: Alex Shi Reviewed-by: Nick Desaulniers Reviewed-by: Miguel Ojeda Signed-off-by: Arnd Bergmann Reviewed-by: Nathan Chancellor Signed-off-by: Masahiro Yamada List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

4d94f910 - Kbuild: use -Wdeclaration-after-statement

Tue, 08 Mar 2022 21:56:13 +0000

Kbuild: use -Wdeclaration-after-statementThe kernel is moving from using `-std=gnu89` to `-std=gnu11`, permittingthe use of additional C11 features such as for-loop initial declarations.One contentious aspect of C99 is that it permits mixed declarations andcode, and for now at least, it seems preferable to enforce thatdeclarations must come first.These warnings were already enabled in the kernel itself, but notfor KBUILD_USERCFLAGS or the compat VDSO on arch/arm64, which usesa separate set of CFLAGS.This patch fixes an existing violation in modpost.c, which is notreported because of the missing flag in KBUILD_USERCFLAGS:| scripts/mod/modpost.c: In function ‘match’:| scripts/mod/modpost.c:837:3: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]| 837 | const char *endp = p + strlen(p) - 1;| | ^~~~~Signed-off-by: Mark Rutland [arnd: don't add a duplicate flag to the default set, update changelog]Signed-off-by: Arnd Bergmann Reviewed-by: Nathan Chancellor Reviewed-by: Nick Desaulniers Tested-by: Sedat Dilek # LLVM/Clang v13.0.0 (x86-64)Signed-off-by: Masahiro Yamada List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

34688c76 - arm64: vdso: remove -nostdlib compiler flag

Sun, 07 Nov 2021 16:18:02 +0000

arm64: vdso: remove -nostdlib compiler flagThe -nostdlib option requests the compiler to not use the standardsystem startup files or libraries when linking. It is effective onlywhen $(CC) is used as a linker driver.Since commit 691efbedc60d ("arm64: vdso: use $(LD) instead of $(CC)to link VDSO"), $(LD) is directly used, hence -nostdlib is unneeded.Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20211107161802.323125-1-masahiroy@kernel.orgSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

3e6f8d1f - arm64: vdso32: require CROSS_COMPILE_COMPAT for gcc+bfd

Tue, 19 Oct 2021 22:36:46 +0000

arm64: vdso32: require CROSS_COMPILE_COMPAT for gcc+bfdSimilar tocommit 231ad7f409f1 ("Makefile: infer --target from ARCH for CC=clang")There really is no point in setting --target based on$CROSS_COMPILE_COMPAT for clang when the integrated assembler is beingused, sincecommit ef94340583ee ("arm64: vdso32: drop -no-integrated-as flag").Allows COMPAT_VDSO to be selected without setting $CROSS_COMPILE_COMPATwhen using clang and lld together.Before:$ ARCH=arm64 CROSS_COMPILE_COMPAT=arm-linux-gnueabi- make -j72 LLVM=1 defconfig$ grep CONFIG_COMPAT_VDSO .configCONFIG_COMPAT_VDSO=y$ ARCH=arm64 make -j72 LLVM=1 defconfig$ grep CONFIG_COMPAT_VDSO .config$After:$ ARCH=arm64 CROSS_COMPILE_COMPAT=arm-linux-gnueabi- make -j72 LLVM=1 defconfig$ grep CONFIG_COMPAT_VDSO .configCONFIG_COMPAT_VDSO=y$ ARCH=arm64 make -j72 LLVM=1 defconfig$ grep CONFIG_COMPAT_VDSO .configCONFIG_COMPAT_VDSO=yReviewed-by: Nathan Chancellor Suggested-by: Nathan Chancellor Tested-by: Nathan Chancellor Signed-off-by: Nick Desaulniers Reviewed-by: Vincenzo Frascino Link: https://lore.kernel.org/r/20211019223646.1146945-5-ndesaulniers@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

14831fad - arm64: vdso32: suppress error message for 'make mrproper'

Tue, 19 Oct 2021 22:36:45 +0000

arm64: vdso32: suppress error message for 'make mrproper'When running the following command without arm-linux-gnueabi-gcc inone's $PATH, the following warning is observed:$ ARCH=arm64 CROSS_COMPILE_COMPAT=arm-linux-gnueabi- make -j72 LLVM=1 mrpropermake[1]: arm-linux-gnueabi-gcc: No such file or directoryThis is because KCONFIG is not run for mrproper, so CONFIG_CC_IS_CLANGis not set, and we end up eagerly evaluating various variables that tryto invoke CC_COMPAT.This is a similar problem to what was observed incommit dc960bfeedb0 ("h8300: suppress error messages for 'make clean'")Reported-by: Lucas Henneman Suggested-by: Masahiro Yamada Signed-off-by: Nick Desaulniers Reviewed-by: Vincenzo Frascino Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor Link: https://lore.kernel.org/r/20211019223646.1146945-4-ndesaulniers@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

a517faa9 - arm64: vdso32: drop test for -march=armv8-a

Tue, 19 Oct 2021 22:36:44 +0000

arm64: vdso32: drop test for -march=armv8-aAs Arnd points out: gcc-4.8 already supported -march=armv8, and we require gcc-5.1 now, so both this #if/#else construct and the corresponding "cc32-option,-march=armv8-a" check should be obsolete now.Link: https://lore.kernel.org/lkml/CAK8P3a3UBEJ0Py2ycz=rHfgog8g3mCOeQOwO0Gmp-iz6Uxkapg@mail.gmail.com/Suggested-by: Arnd Bergmann Signed-off-by: Nick Desaulniers Reviewed-by: Vincenzo Frascino Reviewed-by: Nathan Chancellor Link: https://lore.kernel.org/r/20211019223646.1146945-3-ndesaulniers@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

1907d3ff - arm64: vdso32: drop the test for dmb ishld

Tue, 19 Oct 2021 22:36:43 +0000

arm64: vdso32: drop the test for dmb ishldBinutils added support for this instruction in commite797f7e0b2bedc9328d4a9a0ebc63ca7a2dbbebc which shipped in 2.24 (justmissing the 2.23 release) but was cherry-picked into 2.23 in commit27a50d6755bae906bc73b4ec1a8b448467f0bea1. Thanks to Christian and Simonfor helping me with the patch archaeology.According to Documentation/process/changes.rst, the minimum supportedversion of binutils is 2.23. Since all supported versions of GAS supportthis instruction, drop the assembler invocation, preprocessorflags/guards, and the cross assembler macro that's now unused.This also avoids a recursive self reference in a follow up cleanuppatch.Cc: Christian Biesinger Cc: Simon Marchi Signed-off-by: Nick Desaulniers Reviewed-by: Vincenzo Frascino Reviewed-by: Nathan Chancellor Link: https://lore.kernel.org/r/20211019223646.1146945-2-ndesaulniers@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

ef943405 - arm64: vdso32: drop -no-integrated-as flag

Tue, 20 Apr 2021 17:44:25 +0000

arm64: vdso32: drop -no-integrated-as flagClang can assemble these files just fine; this is a relic from the toplevel Makefile conditionally adding this. We no longer need --prefix,--gcc-toolchain, or -Qunused-arguments flags either with this change, soremove those too.To test building:$ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- \ CROSS_COMPILE_COMPAT=arm-linux-gnueabi- make LLVM=1 LLVM_IAS=1 \ defconfig arch/arm64/kernel/vdso32/Suggested-by: Nathan Chancellor Signed-off-by: Nick Desaulniers Reviewed-by: Nathan Chancellor Reviewed-by: Vincenzo Frascino Tested-by: Stephen Boyd Acked-by: Will Deacon Link: https://lore.kernel.org/r/20210420174427.230228-1-ndesaulniers@google.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile

a5b8ca97 - arm64: do not descend to vdso directories twice

Fri, 18 Dec 2020 02:45:40 +0000

arm64: do not descend to vdso directories twicearm64 descends into each vdso directory twice; first in vdso_prepare,second during the ordinary build process.PPC mimicked it and uncovered a problem [1]. In the first descend,Kbuild directly visits the vdso directories, therefore it does notinherit subdir-ccflags-y from upper directories.This means the command line parameters may differ between the two.If it happens, the offset values in the generated headers might bedifferent from real offsets of vdso.so in the kernel.This potential danger should be avoided. The vdso directories arebuilt in the vdso_prepare stage, so the second descend is unneeded.[1]: https://lore.kernel.org/linux-kbuild/CAK7LNARAkJ3_-4gX0VA2UkapbOftuzfSTVMBbgbw=HD8n7N+7w@mail.gmail.com/T/#ma10dcb961fda13f36d42d58fa6cb2da988b7e73aSigned-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20201218024540.1102650-1-masahiroy@kernel.orgSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/kernel/vdso32/Makefile