Changes in mkcompile_h

a6c26e38 - Revert "kbuild: Make scripts/compile.h when sh != bash"

Sun, 28 Aug 2022 02:39:56 +0000

Revert "kbuild: Make scripts/compile.h when sh != bash"This reverts commit [1] in the pre-git era.I do not know what problem happened in the script when sh != bashbecause there is no commit message.Now that this script is much simpler than it used to be, let's revertit, and let' see. (If this turns out to be problematic, fix the codewith proper commit description.)[1]: https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/commit/?id=11acbbbb8a50f4de7dbe4bc1b5acc440dfe81810Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

c7b594f5 - scripts/mkcompile_h: move LC_ALL=C to '$LD -v'

Sun, 28 Aug 2022 02:39:55 +0000

scripts/mkcompile_h: move LC_ALL=C to '$LD -v'Minimize the scope of LC_ALL=C like before commit 87c94bfb8ad3 ("kbuild:override build timestamp & version").Give LC_ALL=C to '$LD -v' to get the consistent version output, as commitbcbcf50f5218 ("kbuild: fix ld-version.sh to not be affected by locale")mentioned the LD version is affected by locale.While I was here, I merged two sed invocations.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

2df8220c - kbuild: build init/built-in.a just once

Sun, 28 Aug 2022 02:39:53 +0000

kbuild: build init/built-in.a just onceKbuild builds init/built-in.a twice; first during the ordinarydirectory descending, second from scripts/link-vmlinux.sh.We do this because UTS_VERSION contains the build version and thetimestamp. We cannot update it during the normal directory traversalsince we do not yet know if we need to update vmlinux. UTS_VERSION istemporarily calculated, but omitted from the update check. Otherwise,vmlinux would be rebuilt every time.When Kbuild results in running link-vmlinux.sh, it increments theversion number in the .version file and takes the timestamp at thattime to really fix UTS_VERSION.However, updating the same file twice is a footgun. To avoid nastytimestamp issues, all build artifacts that depend on init/built-in.aare atomically generated in link-vmlinux.sh, where some of them do notneed rebuilding.To fix this issue, this commit changes as follows:[1] Split UTS_VERSION out to include/generated/utsversion.h from include/generated/compile.h include/generated/utsversion.h is generated just before the vmlinux link. It is generated under include/generated/ because some decompressors (s390, x86) use UTS_VERSION.[2] Split init_uts_ns and linux_banner out to init/version-timestamp.c from init/version.c init_uts_ns and linux_banner contain UTS_VERSION. During the ordinary directory descending, they are compiled with __weak and used to determine if vmlinux needs relinking. Just before the vmlinux link, they are compiled without __weak to embed the real version and timestamp.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

a0a7e453 - sched/preempt: Tell about PREEMPT_DYNAMIC on kernel headers

Thu, 17 Feb 2022 11:12:40 +0000

sched/preempt: Tell about PREEMPT_DYNAMIC on kernel headersDisplaying "PREEMPT" on kernel headers when CONFIG_PREEMPT_DYNAMIC=ycan be misleading for anybody involved in remote debugging because itis then not guaranteed that there is an actual preemption behaviour. Itdepends on default Kconfig or boot defined choices.Therefore, tell about PREEMPT_DYNAMIC on static kernel headers and leavethe search for the actual preemption behaviour to browsing dmesg.Reviewed-by: Valentin Schneider Signed-off-by: Frederic Weisbecker Signed-off-by: Peter Zijlstra (Intel) Link: https://lkml.kernel.org/r/20220217111240.GA742892@lothringen List of files: /linux-6.15/scripts/mkcompile_h

a979522a - kbuild: mkcompile_h: consider timestamp if KBUILD_BUILD_TIMESTAMP is set

Sat, 12 Jun 2021 14:18:38 +0000

kbuild: mkcompile_h: consider timestamp if KBUILD_BUILD_TIMESTAMP is setTo avoid unnecessary recompilations, mkcompile_h does not regeneratecompile.h if just the timestamp changed.Though, if KBUILD_BUILD_TIMESTAMP is set, an explicit timestamp for thebuild was requested, in which case we should not ignore it.If a user follows the documentation for reproducible builds [1] anddefines KBUILD_BUILD_TIMESTAMP as the git commit timestamp, a cleanbuild will have the correct timestamp. A subsequent cherry-pick (oramend) changes the commit timestamp and if an incremental build is donewith a different KBUILD_BUILD_TIMESTAMP now, that new value is not takeninto consideration. But it should for reproducibility.Hence, whenever KBUILD_BUILD_TIMESTAMP is explicitly set, do not ignoreUTS_VERSION when making a decision about whether the regenerated versionof compile.h should be moved into place.[1] https://www.kernel.org/doc/html/latest/kbuild/reproducible-builds.htmlSigned-off-by: Matthias Maennich Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

c39013ee - kbuild: clean up ${quiet} checks in shell scripts

Mon, 17 May 2021 07:03:14 +0000

kbuild: clean up ${quiet} checks in shell scriptsThere were efforts to make 'make -s' really silent when it is awarning-free build.The conventional way was to let a shell script check ${quiet}, and ifit is 'silent_', suppress the stdout by itself.With the previous commit, the 'cmd' takes care of it now. The 'cmd' isalso invoked from if_changed, if_changed_dep, and if_changed_rule.You can omit ${quiet} checks in shell scripts when they are invokedfrom the 'cmd' macro.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

1e66d50a - kbuild: Use uname for LINUX_COMPILE_HOST detection

Tue, 20 Oct 2020 09:34:59 +0000

kbuild: Use uname for LINUX_COMPILE_HOST detection`hostname` may not be present on some systems as it's not mandated byPOSIX/SUSv4. This isn't just a theoretical problem: on Arch Linux,`hostname` is provided by `inetutils`, which isn't part of the basedistribution. ./scripts/mkcompile_h: line 38: hostname: command not foundUse `uname -n` instead, which is more likely to be available (andmandated by standards).Signed-off-by: Chris Down Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

9a950154 - kbuild: use CONFIG_CC_VERSION_TEXT to construct LINUX_COMPILER macro

Thu, 23 Apr 2020 14:23:54 +0000

kbuild: use CONFIG_CC_VERSION_TEXT to construct LINUX_COMPILER macroscripts/mkcompile_h runs $(CC) just for getting the version string.Reuse CONFIG_CC_VERSION_TEXT for optimization.For GCC, this slightly changes the version string. I do not think itis a big deal as we do not have the defined format for LINUX_COMPILER.In fact, the recent commit 4dcc9a88448a ("kbuild: mkcompile_h:Include $LD version in /proc/version") added the linker version.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

4dcc9a88 - kbuild: mkcompile_h: Include $LD version in /proc/version

Thu, 02 Apr 2020 08:18:37 +0000

kbuild: mkcompile_h: Include $LD version in /proc/versionWhen doing Clang builds of the kernel, it is possible to link witheither ld.bfd (binutils) or ld.lld (LLVM), but it is not possible todiscover this from a running kernel. Add the "$LD -v" output to/proc/version.Signed-off-by: Kees Cook Reviewed-by: Nick Desaulniers Tested-by: Nick Desaulniers Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor Reviewed-by: Fangrui Song Reviewed-by: Sedat Dilek Tested-by: Sedat Dilek Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

f84fdf8d - kbuild: remove the owner check in mkcompile_h

Sat, 15 Feb 2020 07:50:20 +0000

kbuild: remove the owner check in mkcompile_hThis reverts a very old commit, which dates back to the pre-git era:|commit 5d1cfb5b12f72145d30ba0f53c9f238144b122b8|Author: Kai Germaschewski |Date: Sat Jul 27 02:53:19 2002 -0500|| kbuild: Fix compiling/installing as different users|| "make bzImage && sudo make install" had the problem that during| the "sudo make install" the build system would notice that the information| in include/linux/compile.h is not accurate (it says "compiled by ",| but we are root), thus causing compile.h to be updated and leading to| some recompiles.|| We now only update "compile.h" if the current user is the owner of| include/linux/autoconf.h, i.e. the user who did the "make *config". So the| above sequence will correctly state "compiled by ".||diff --git a/scripts/mkcompile_h b/scripts/mkcompile_h|index 6313db96172..cd956380978 100755|--- a/scripts/mkcompile_h|+++ b/scripts/mkcompile_h|@@ -3,6 +3,17 @@ ARCH=$2| SMP=$3| CC=$4||+# If compile.h exists already and we don't own autoconf.h|+# (i.e. we're not the same user who did make *config), don't|+# modify compile.h|+# So "sudo make install" won't change the "compiled by "|+# do "compiled by root"|+|+if [ -r $TARGET -a ! -O ../include/linux/autoconf.h ]; then|+ echo ' (not modified)'|+ exit 0|+fi|+| if [ -r ../.version ]; then| VERSION=`cat ../.version`| elseThe 'make bzImage && sudo make install' problem no longer happensbecause commit 1648e4f80506 ("x86, kbuild: make "make install" notdepend on vmlinux") fixed the root cause.Commit 19514fc665ff ("arm, kbuild: make "make install" not depend onvmlinux") fixed the similar issue on ARM, with detailed explanation.So, the rule is that the installation targets should never triggerthe builds of any build artifact. By following it, this check isunneeded.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

c8f3dea9 - mkcompile_h: use printf for LINUX_COMPILE_BY

Fri, 06 Dec 2019 13:03:02 +0000

mkcompile_h: use printf for LINUX_COMPILE_BYCommit 858805b336be ("kbuild: add $(BASH) to run scripts withbash-extension") shed light on portability issues. Here is another one.Since commit f07726048d59 ("Fix handling of backlash character inLINUX_COMPILE_BY name"), we must escape a backslash contained inLINUX_COMPILE_BY. This is not working on such distros as Ubuntu.As the POSIX spec [1] says, if any of the operands contain a backslash( '\' ) character, the results are implementation-defined.The actual shell of /bin/sh could be bash, dash, etc. depending ondistros, and the behavior of builtin echo command is different amongthem.The bash builtin echo, unless -e is given, copies the arguments tostdout without expanding escape sequences (BSD-like behavior).The dash builtin echo, in contrast, adopts System V behavior, whichdoes expand escape sequences without any option given.Even non-builtin /bin/echo behaves differently depending on the system.Due to these variations, echo is considered as a non-portable command.Using printf is the common solution to avoid the portability issue.[1] https://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.htmlFixes: 858805b336be ("kbuild: add $(BASH) to run scripts with bash-extension")Reported-by: XXing Wei Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

e8193650 - mkcompile_h: git rid of UTS_TRUNCATE from LINUX_COMPILE_{BY,HOST}

Fri, 06 Dec 2019 13:03:01 +0000

mkcompile_h: git rid of UTS_TRUNCATE from LINUX_COMPILE_{BY,HOST}UTS_VERSION is set to struct uts_namespace, hence a too long stringshould be truncated so it fits in 64 characters.On the other hand, LINUX_COMPILE_BY/HOST are not set to uts_namespace.They are just used in the banners, which do not have specific lengthlimitation.I dug into the git history, but I could not find the reason whythese two strings must fit in 64 characters. Remove them.Now that UTS_VERSION is the only user of UTS_TRUNCATE, I squashed it.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

4b950bb9 - Kbuild: Handle PREEMPT_RT for version string and magic

Sun, 28 Jul 2019 18:27:41 +0000

Kbuild: Handle PREEMPT_RT for version string and magicUpdate the build scripts and the version magic to reflect whenCONFIG_PREEMPT_RT is enabled in the same way as CONFIG_PREEMPT is treated.The resulting version strings: Linux m 5.3.0-rc1+ #100 SMP Fri Jul 26 ... Linux m 5.3.0-rc1+ #101 SMP PREEMPT Fri Jul 26 ... Linux m 5.3.0-rc1+ #102 SMP PREEMPT_RT Fri Jul 26 ...The module vermagic: 5.3.0-rc1+ SMP mod_unload modversions 5.3.0-rc1+ SMP preempt mod_unload modversions 5.3.0-rc1+ SMP preempt_rt mod_unload modversionsSigned-off-by: Thomas Gleixner Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

b79c6aa6 - kbuild: remove unnecessary in-subshell execution

Thu, 17 Jan 2019 10:02:44 +0000

kbuild: remove unnecessary in-subshell executionThe commands surrounded by ( ) are executed in a subshell, but inmost cases, we do not need to spawn an extra subshell.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/scripts/mkcompile_h

37131ec4 - kbuild: mkcompile_h: do not create .version

Fri, 22 Sep 2017 05:31:14 +0000

kbuild: mkcompile_h: do not create .versionThis script does not need to create .version; it will be created byscripts/link-vmlinux.sh later. Clean-up the code slightly.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

adcc3f7c - scripts/mkcompile_h: Remove trailing spaces from compiler version

Mon, 12 Jun 2017 08:23:17 +0000

scripts/mkcompile_h: Remove trailing spaces from compiler versionImproves the output of "cat /proc/version" by getting rid of thetrailing space at the end of the compiler version when the kernelis compiled using GCC.Signed-off-by: Jonathan Liu Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/mkcompile_h

38385f8f - kbuild: trivial - remove trailing spaces

Mon, 28 Apr 2014 07:26:18 +0000

kbuild: trivial - remove trailing spacesSigned-off-by: Masahiro Yamada Signed-off-by: Michal Marek List of files: /linux-6.15/scripts/mkcompile_h

db46293b - kbuild: LLVMLinux: Fix LINUX_COMPILER definition script for compilation with clang

Wed, 14 Nov 2012 09:55:48 +0000

kbuild: LLVMLinux: Fix LINUX_COMPILER definition script for compilation with clangWhen building the LINUX_COMPILER definition, instead of merely taking the lastline from "$(CC) -v", grep for ' version ' in the output. This supports bothgcc and clang.Signed-off-by: Jan-Simon Möller Signed-off-by: Behan Webster Signed-off-by: Mark Charlebois Cc: PaX Team List of files: /linux-6.15/scripts/mkcompile_h

f0772604 - Fix handling of backlash character in LINUX_COMPILE_BY name

Mon, 25 Apr 2011 12:35:21 +0000

Fix handling of backlash character in LINUX_COMPILE_BY nameWhen using a domain login, `whoami` returns the login inuser\domain format. This leads to either warnings on unrecognisedescape sequences or escaped characters being generated for the user.This patch ensures that any backslash is escaped to a double-backslashto make sure the name is preserved correctly. This patch does notenforce escaping on the KBUILD_BUILD_USER variable, as this is somethingthe user has control of and can escape if required.Signed-off-by: Marcin Nowakowski Signed-off-by: Michal Marek List of files: /linux-6.15/scripts/mkcompile_h