Changes in Makefile

83c0b272 - initramfs_test: kunit tests for initramfs unpacking

Tue, 04 Mar 2025 05:57:45 +0000

initramfs_test: kunit tests for initramfs unpackingProvide some basic initramfs unpack sanity tests covering:- simple file / dir extraction- filename field overrun, as reported and fixed separately via https://lore.kernel.org/r/20241030035509.20194-2-ddiss@suse.de- "070702" cpio data checksums- hardlinksSigned-off-by: David Disseldorp Link: https://lore.kernel.org/r/20250304061020.9815-3-ddiss@suse.deSigned-off-by: Christian Brauner List of files: /linux-6.15/init/Makefile

ae4c4cee - kbuild: move init/build-version to scripts/

Tue, 11 Jun 2024 18:24:47 +0000

kbuild: move init/build-version to scripts/At first, I thought this script would be needed only in init/Makefile.However, commit 5db8face97f8 ("kbuild: Restore .version auto-incrementbehaviour for Debian packages") and commit 1789fc912541 ("kbuild:rpm-pkg: invoke the kernel build from rpmbuild for binrpm-pkg")revealed that it was actually needed for scripts/package/mk* as well.After all, scripts/ is a better place for it.Signed-off-by: Masahiro Yamada Reviewed-by: Nathan Chancellor List of files: /linux-6.15/init/Makefile

7f7f6f7a - Makefile: remove redundant tool coverage variables

Mon, 06 May 2024 13:35:43 +0000

Makefile: remove redundant tool coverage variablesNow Kbuild provides reasonable defaults for objtool, sanitizers, andprofilers.Remove redundant variables.Note:This commit changes the coverage for some objects: - include arch/mips/vdso/vdso-image.o into UBSAN, GCOV, KCOV - include arch/sparc/vdso/vdso-image-*.o into UBSAN - include arch/sparc/vdso/vma.o into UBSAN - include arch/x86/entry/vdso/extable.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vdso-image-*.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vdso32-setup.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vma.o into GCOV, KCOV - include arch/x86/um/vdso/vma.o into KASAN, GCOV, KCOVI believe these are positive effects because all of them are kernelspace objects.Signed-off-by: Masahiro Yamada Reviewed-by: Kees Cook Tested-by: Roberto Sassu List of files: /linux-6.15/init/Makefile

b1992c37 - kbuild: use $(src) instead of $(srctree)/$(src) for source directory

Sat, 27 Apr 2024 14:55:02 +0000

kbuild: use $(src) instead of $(srctree)/$(src) for source directoryKbuild conventionally uses $(obj)/ for generated files, and $(src)/ forchecked-in source files. It is merely a convention without any functionaldifference. In fact, $(obj) and $(src) are exactly the same, as definedin scripts/Makefile.build: src := $(obj)When the kernel is built in a separate output directory, $(src) doesnot accurately reflect the source directory location. While Kbuildresolves this discrepancy by specifying VPATH=$(srctree) to search forsource files, it does not cover all cases. For example, when adding aheader search path for local headers, -I$(srctree)/$(src) is typicallypassed to the compiler.This introduces inconsistency between upstream and downstream Makefilesbecause $(src) is used instead of $(srctree)/$(src) for the latter.To address this inconsistency, this commit changes the semantics of$(src) so that it always points to the directory in the source tree.Going forward, the variables used in Makefiles will have the followingmeanings: $(obj) - directory in the object tree $(src) - directory in the source tree (changed by this commit) $(objtree) - the top of the kernel object tree $(srctree) - the top of the kernel source treeConsequently, $(srctree)/$(src) in upstream Makefiles need to be replacedwith $(src).Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier List of files: /linux-6.15/init/Makefile

2d7ce49f - x86/retpoline: Make sure there are no unconverted return thunks due to KCSAN

Tue, 17 Oct 2023 16:59:46 +0000

x86/retpoline: Make sure there are no unconverted return thunks due to KCSANEnabling CONFIG_KCSAN leads to unconverted, default return thunks toremain after patching.As David Kaplan describes in his debugging of the issue, it is caused bya couple of KCSAN-generated constructors which aren't processed byobjtool: "When KCSAN is enabled, GCC generates lots of constructor functions named _sub_I_00099_0 which call __tsan_init and then return. The returns in these are generally annotated normally by objtool and fixed up at runtime. But objtool runs on vmlinux.o and vmlinux.o does not include a couple of object files that are in vmlinux, like init/version-timestamp.o and .vmlinux.export.o, both of which contain _sub_I_00099_0 functions. As a result, the returns in these functions are not annotated, and the panic occurs when we call one of them in do_ctors and it uses the default return thunk. This difference can be seen by counting the number of these functions in the object files: $ objdump -d vmlinux.o|grep -c "<_sub_I_00099_0>:" 2601 $ objdump -d vmlinux|grep -c "<_sub_I_00099_0>:" 2603 If these functions are only run during kernel boot, there is no speculation concern."Fix it by disabling KCSAN on version-timestamp.o and .vmlinux.export.oso the extra functions don't get generated. KASAN and GCOV are alreadydisabled for those files. [ bp: Massage commit message. ]Closes: https://lore.kernel.org/lkml/20231016214810.GA3942238@dev-arch.thelio-3990X/Reported-by: Nathan Chancellor Signed-off-by: Josh Poimboeuf Signed-off-by: Borislav Petkov (AMD) Reviewed-by: Nick Desaulniers Acked-by: Marco Elver Tested-by: Nathan Chancellor Link: https://lore.kernel.org/r/20231017165946.v4i2d4exyqwqq3bx@treble List of files: /linux-6.15/init/Makefile

ddf56288 - kbuild: Fix CFI failures with GCOV

Fri, 23 Jun 2023 00:11:42 +0000

kbuild: Fix CFI failures with GCOVWith GCOV_PROFILE_ALL, Clang injects __llvm_gcov_* functions toeach object file, and the functions are indirectly called duringboot. However, when code is injected to object files that are notpart of vmlinux.o, it's also not processed by objtool, which breaksCFI hash randomization as the hashes in these files won't beincluded in the .cfi_sites section and thus won't be randomized.Similarly to commit 42633ed852de ("kbuild: Fix CFI hashrandomization with KASAN"), disable GCOV for .vmlinux.export.o andinit/version-timestamp.o to avoid emitting unnecessary functions toobject files that don't otherwise have executable code.Fixes: 0c3e806ec0f9 ("x86/cfi: Add boot time hash randomization")Reported-by: Joe Fradley Signed-off-by: Sami Tolvanen Acked-by: Peter Zijlstra (Intel) Reviewed-by: Kees Cook Reviewed-by: Nick Desaulniers Signed-off-by: Masahiro Yamada List of files: /linux-6.15/init/Makefile

42633ed8 - kbuild: Fix CFI hash randomization with KASAN

Thu, 12 Jan 2023 22:49:48 +0000

kbuild: Fix CFI hash randomization with KASANClang emits a asan.module_ctor constructor to each object filewhen KASAN is enabled, and these functions are indirectly calledin do_ctors. With CONFIG_CFI_CLANG, the compiler also emits a CFItype hash before each address-taken global function so they canpass indirect call checks.However, in commit 0c3e806ec0f9 ("x86/cfi: Add boot time hashrandomization"), x86 implemented boot time hash randomization,which relies on the .cfi_sites section generated by objtool. Asobjtool is run against vmlinux.o instead of individual objectfiles with X86_KERNEL_IBT (enabled by default), CFI types inobject files that are not part of vmlinux.o end up not beingincluded in .cfi_sites, and thus won't get randomized and tripCFI when called.Only .vmlinux.export.o and init/version-timestamp.o are linkedinto vmlinux separately from vmlinux.o. As these files don'tcontain any functions, disable KASAN for both of them to avoidbreaking hash randomization.Link: https://github.com/ClangBuiltLinux/linux/issues/1742Fixes: 0c3e806ec0f9 ("x86/cfi: Add boot time hash randomization")Signed-off-by: Sami Tolvanen Acked-by: Peter Zijlstra (Intel) Signed-off-by: Kees Cook Link: https://lore.kernel.org/r/20230112224948.1479453-2-samitolvanen@google.com List of files: /linux-6.15/init/Makefile

a55f283e - kbuild: generate include/generated/compile.h in top Makefile

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

kbuild: generate include/generated/compile.h in top MakefileNow that UTS_VERSION was separated out, this header can be generatedmuch earlier, and probably the top Makefile is a better place to do itthan init/Makefile.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/init/Makefile

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/init/Makefile

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/init/Makefile

129ab0d2 - kbuild: do not quote string values in include/config/auto.conf

Tue, 14 Dec 2021 02:53:53 +0000

kbuild: do not quote string values in include/config/auto.confThe previous commit fixed up all shell scripts to not includeinclude/config/auto.conf.Now that include/config/auto.conf is only included by Makefiles,we can change it into a more Make-friendly form.Previously, Kconfig output string values enclosed with double-quotes(both in the .config and include/config/auto.conf): CONFIG_X="foo bar"Unlike shell, Make handles double-quotes (and single-quotes as well)verbatim. We must rip them off when used.There are some patterns: [1] $(patsubst "%",%,$(CONFIG_X)) [2] $(CONFIG_X:"%"=%) [3] $(subst ",,$(CONFIG_X)) [4] $(shell echo $(CONFIG_X))These are not only ugly, but also fragile.[1] and [2] do not work if the value contains spaces, like CONFIG_X=" foo bar "[3] does not work correctly if the value contains double-quotes like CONFIG_X="foo\"bar"[4] seems to work better, but has a cost of forking a process.Anyway, quoted strings were always PITA for our Makefiles.This commit changes Kconfig to stop quoting in include/config/auto.conf.These are the string type symbols referenced in Makefiles or scripts: ACPI_CUSTOM_DSDT_FILE ARC_BUILTIN_DTB_NAME ARC_TUNE_MCPU BUILTIN_DTB_SOURCE CC_IMPLICIT_FALLTHROUGH CC_VERSION_TEXT CFG80211_EXTRA_REGDB_KEYDIR EXTRA_FIRMWARE EXTRA_FIRMWARE_DIR EXTRA_TARGETS H8300_BUILTIN_DTB INITRAMFS_SOURCE LOCALVERSION MODULE_SIG_HASH MODULE_SIG_KEY NDS32_BUILTIN_DTB NIOS2_DTB_SOURCE OPENRISC_BUILTIN_DTB SOC_CANAAN_K210_DTB_SOURCE SYSTEM_BLACKLIST_HASH_LIST SYSTEM_REVOCATION_KEYS SYSTEM_TRUSTED_KEYS TARGET_CPU UNUSED_KSYMS_WHITELIST XILINX_MICROBLAZE0_FAMILY XILINX_MICROBLAZE0_HW_VER XTENSA_VARIANT_NAMEI checked them one by one, and fixed up the code where necessary.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/init/Makefile

a8b76910 - preempt: Restore preemption model selection configs

Wed, 10 Nov 2021 20:24:44 +0000

preempt: Restore preemption model selection configsCommit c597bfddc9e9 ("sched: Provide Kconfig support for default dynamicpreempt mode") changed the selectable config names for the preemptionmodel. This means a config file must now select CONFIG_PREEMPT_BEHAVIOUR=yrather than CONFIG_PREEMPT=yto get a preemptible kernel. This means all arch config files would need tobe updated - right now they'll all end up with the defaultCONFIG_PREEMPT_NONE_BEHAVIOUR.Rather than touch a good hundred of config files, restore usage ofCONFIG_PREEMPT{_NONE, _VOLUNTARY}. Make them configure:o The build-time preemption model when !PREEMPT_DYNAMICo The default boot-time preemption model when PREEMPT_DYNAMICAdd siblings of those configs with the _BUILD suffix to unconditionallydesignate the build-time preemption model (PREEMPT_DYNAMIC is built withthe "highest" preemption model it supports, aka PREEMPT). Downstreamconfigs should by now all be depending / selected by CONFIG_PREEMPTIONrather than CONFIG_PREEMPT, so only a few sites need patching up.Signed-off-by: Valentin Schneider Signed-off-by: Peter Zijlstra (Intel) Acked-by: Marco Elver Link: https://lore.kernel.org/r/20211110202448.4054153-2-valentin.schneider@arm.com List of files: /linux-6.15/init/Makefile

41eba23e - init: use $(call cmd,) for generating include/generated/compile.h

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

init: use $(call cmd,) for generating include/generated/compile.hThe 'cmd' macro shows the short log only when $(quiet) is quiet_.Do not do it manually.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/init/Makefile

4f5b246b - md: move the early init autodetect code to drivers/md/

Sun, 07 Jun 2020 14:18:59 +0000

md: move the early init autodetect code to drivers/md/Just like the NFS and CIFS root code this better lives with thedriver it is tightly integrated with.Signed-off-by: Christoph Hellwig Acked-by: Song Liu Acked-by: Linus Torvalds List of files: /linux-6.15/init/Makefile

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/init/Makefile

01a6126b - kbuild: do not pass $(KBUILD_CFLAGS) to scripts/mkcompile_h

Fri, 03 Apr 2020 21:24:59 +0000

kbuild: do not pass $(KBUILD_CFLAGS) to scripts/mkcompile_hscripts/mkcompile_h uses $(CC) only for getting the version string.I suspected there was a specific reason why the additional flags wereneeded, and dug the commit history. This code dates back to at least2002 [1], but I could not get any more clue.Just get rid of it.[1]: https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/commit/?id=29f3df7eba8ddf91a55183f9967f76fbcc3ab742Signed-off-by: Masahiro Yamada Reviewed-by: Kees Cook List of files: /linux-6.15/init/Makefile

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/init/Makefile

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/init/Makefile

0500871f - Construct init thread stack in the linker script rather than by union

Tue, 02 Jan 2018 15:12:01 +0000

Construct init thread stack in the linker script rather than by unionConstruct the init thread stack in the linker script rather than doing itby means of a union so that ia64's init_task.c can be got rid of.The following symbols are then made available from INIT_TASK_DATA() linkerscript macro: init_thread_union init_stackINIT_TASK_DATA() also expands the region to THREAD_SIZE to accommodate thesize of the init stack. init_thread_union is given its own section so thatit can be placed into the stack space in the right order. I'm assumingthat the ia64 ordering is correct and that the task_struct is first and thethread_info second.Signed-off-by: David Howells Tested-by: Tony Luck Tested-by: Will Deacon (arm64)Tested-by: Palmer Dabbelt Acked-by: Thomas Gleixner List of files: /linux-6.15/init/Makefile

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/init/Makefile