Changes in Makefile

9c3681f9 - kbuild: Add gendwarfksyms as an alternative to genksyms

Fri, 03 Jan 2025 20:45:39 +0000

kbuild: Add gendwarfksyms as an alternative to genksymsWhen MODVERSIONS is enabled, allow selecting gendwarfksyms as theimplementation, but default to genksyms.Signed-off-by: Sami Tolvanen Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

f2856884 - tools: Add gendwarfksyms

Fri, 03 Jan 2025 20:45:23 +0000

tools: Add gendwarfksymsAdd a basic DWARF parser, which uses libdw to traverse the debugginginformation in an object file and looks for functions and variables.In follow-up patches, this will be expanded to produce symbol versionsfor CONFIG_MODVERSIONS from DWARF.Signed-off-by: Sami Tolvanen Reviewed-by: Petr Pavlu Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

41d7ea30 - lib: packing: add pack_fields() and unpack_fields()

Tue, 10 Dec 2024 20:27:12 +0000

lib: packing: add pack_fields() and unpack_fields()This is new API which caters to the following requirements:- Pack or unpack a large number of fields to/from a buffer with a small code footprint. The current alternative is to open-code a large number of calls to pack() and unpack(), or to use packing() to reduce that number to half. But packing() is not const-correct.- Use unpacked numbers stored in variables smaller than u64. This reduces the rodata footprint of the stored field arrays.- Perform error checking at compile time, rather than runtime, and return void from the API functions. Because the C preprocessor can't generate variable length code (loops), this is a bit tricky to do with macros. To handle this, implement macros which sanity check the packed field definitions based on their size. Finally, a single macro with a chain of __builtin_choose_expr() is used to select the appropriate macros. We enforce the use of ascending or descending order to avoid O(N^2) scaling when checking for overlap. Note that the macros are written with care to ensure that the compilers can correctly evaluate the resulting code at compile time. In particular, care was taken with avoiding too many nested statement expressions. Nested statement expressions trip up some compilers, especially when passing down variables created in previous statement expressions. There are two key design choices intended to keep the overall macro code size small. First, the definition of each CHECK_PACKED_FIELDS_N macro is implemented recursively, by calling the N-1 macro. This avoids needing the code to repeat multiple times. Second, the CHECK_PACKED_FIELD macro enforces that the fields in the array are sorted in order. This allows checking for overlap only with neighboring fields, rather than the general overlap case where each field would need to be checked against other fields. The overlap checks use the first two fields to determine the order of the remaining fields, thus allowing either ascending or descending order. This enables drivers the flexibility to keep the fields ordered in which ever order most naturally fits their hardware design and its associated documentation. The CHECK_PACKED_FIELDS macro is directly called from within pack_fields and unpack_fields, ensuring that all drivers using the API receive the benefits of the compile-time checks. Users do not need to directly call any of the macros directly. The CHECK_PACKED_FIELDS and its helper macros CHECK_PACKED_FIELDS_(0..50) are generated using a simple C program in scripts/gen_packed_field_checks.c This program can be compiled on demand and executed to generate the macro code in include/linux/packing.h. This will aid in the event that a driver needs more than 50 fields. The generator can be updated with a new size, and used to update the packing.h header file. In practice, the ice driver will need to support 27 fields, and the sja1105 driver will need to support 0 fields. This on-demand generation avoids the need to modify Kbuild. We do not anticipate the maximum number of fields to grow very often.- Reduced rodata footprint for the storage of the packed field arrays. To that end, we have struct packed_field_u8 and packed_field_u16, which define the fields with the associated type. More can be added as needed (unlikely for now). On these types, the same generic pack_fields() and unpack_fields() API can be used, thanks to the new C11 _Generic() selection feature, which can call pack_fields_u8() or pack_fields_16(), depending on the type of the "fields" array - a simplistic form of polymorphism. It is evaluated at compile time which function will actually be called.Over time, packing() is expected to be completely replaced either withpack() or with pack_fields().Signed-off-by: Vladimir Oltean Co-developed-by: Jacob Keller Signed-off-by: Jacob Keller Reviewed-by: Vladimir Oltean Link: https://patch.msgid.link/20241210-packing-pack-fields-and-ice-implementation-v10-3-ee56a47479ac@intel.comSigned-off-by: Jakub Kicinski List of files: /linux-6.15/scripts/Makefile

ba199dc9 - scripts: add boot policy generation program

Sat, 03 Aug 2024 06:08:31 +0000

scripts: add boot policy generation programEnables an IPE policy to be enforced from kernel start, enabling accesscontrol based on trust from kernel startup. This is accomplished bytransforming an IPE policy indicated by CONFIG_IPE_BOOT_POLICY into ac-string literal that is parsed at kernel startup as an unsigned policy.Signed-off-by: Deven Bowers Signed-off-by: Fan Wu Signed-off-by: Paul Moore List of files: /linux-6.15/scripts/Makefile

ab0f4ced - arch: um: rust: Add i386 support for Rust

Tue, 04 Jun 2024 22:40:50 +0000

arch: um: rust: Add i386 support for RustAt present, Rust in the kernel only supports 64-bit x86, so UML hasfollowed suit. However, it's significantly easier to support 32-bit i386on UML than on bare metal, as UML does not use the -mregparm option(which alters the ABI), which is not yet supported by rustc[1].Add support for CONFIG_RUST on um/i386, by adding a new target config togenerate_rust_target, and replacing various checks on CONFIG_X86_64 toalso support CONFIG_X86_32.We still use generate_rust_target, rather than a built-in rustc target,in order to match x86_64, provide a future place for -mregparm, and moreeasily disable floating point instructions.With these changes, the KUnit tests pass with:kunit.py run --make_options LLVM=1 --kconfig_add CONFIG_RUST=y--kconfig_add CONFIG_64BIT=n --kconfig_add CONFIG_FORTIFY_SOURCE=nAn earlier version of these changes was proposed on the Rust-for-Linuxgithub[2].[1]: https://github.com/rust-lang/rust/issues/116972[2]: https://github.com/Rust-for-Linux/linux/pull/966Signed-off-by: David Gow Link: https://patch.msgid.link/20240604224052.3138504-1-davidgow@google.comSigned-off-by: Johannes Berg List of files: /linux-6.15/scripts/Makefile

8f8d74ee - LoongArch: rust: Switch to use built-in rustc target

Tue, 14 May 2024 04:24:18 +0000

LoongArch: rust: Switch to use built-in rustc targetThis commit switches to use the LoongArch's built-in rustc target'loongarch64-unknown-none-softfloat'. The Rust samples have been tested.Acked-by: Miguel Ojeda Tested-by: Miguel Ojeda Signed-off-by: WANG Rui Signed-off-by: Huacai Chen List of files: /linux-6.15/scripts/Makefile

cb8a2ef0 - LoongArch: Add ORC stack unwinder support

Mon, 11 Mar 2024 14:23:47 +0000

LoongArch: Add ORC stack unwinder supportThe kernel CONFIG_UNWINDER_ORC option enables the ORC unwinder, which issimilar in concept to a DWARF unwinder. The difference is that the formatof the ORC data is much simpler than DWARF, which in turn allows the ORCunwinder to be much simpler and faster.The ORC data consists of unwind tables which are generated by objtool.After analyzing all the code paths of a .o file, it determines informationabout the stack state at each instruction address in the file and outputsthat information to the .orc_unwind and .orc_unwind_ip sections.The per-object ORC sections are combined at link time and are sorted andpost-processed at boot time. The unwinder uses the resulting data tocorrelate instruction addresses with their stack states at run time.Most of the logic are similar with x86, in order to get ra info before rais saved into stack, add ra_reg and ra_offset into orc_entry. At the sametime, modify some arch-specific code to silence the objtool warnings.Co-developed-by: Jinyang He Signed-off-by: Jinyang He Co-developed-by: Youling Tang Signed-off-by: Youling Tang Signed-off-by: Tiezhu Yang Signed-off-by: Huacai Chen List of files: /linux-6.15/scripts/Makefile

f82811e2 - rust: Refactor the build target to allow the use of builtin targets

Fri, 20 Oct 2023 15:50:55 +0000

rust: Refactor the build target to allow the use of builtin targetsEventually we want all architectures to be using the target as definedby rustc. However currently some architectures can't do that and areusing the target.json specification. This puts in place the foundationto allow the use of the builtin target definition or a target.jsonspecification.Signed-off-by: Jamie Cunliffe Acked-by: Masahiro Yamada Tested-by: Alice Ryhl Link: https://lore.kernel.org/r/20231020155056.3495121-2-Jamie.Cunliffe@arm.com[catalin.marinas@arm.com: squashed loongarch ifneq fix from WANG Rui]Signed-off-by: Catalin Marinas List of files: /linux-6.15/scripts/Makefile

a66d733d - rust: support running Rust documentation tests as KUnit ones

Tue, 18 Jul 2023 05:27:51 +0000

rust: support running Rust documentation tests as KUnit onesRust has documentation tests: these are typically examples ofusage of any item (e.g. function, struct, module...).They are very convenient because they are just writtenalongside the documentation. For instance: /// Sums two numbers. /// /// ``` /// assert_eq!(mymod::f(10, 20), 30); /// ``` pub fn f(a: i32, b: i32) -> i32 { a + b }In userspace, the tests are collected and run via `rustdoc`.Using the tool as-is would be useful already, since it allowsto compile-test most tests (thus enforcing they are keptin sync with the code they document) and run those that do notdepend on in-kernel APIs.However, by transforming the tests into a KUnit test suite,they can also be run inside the kernel. Moreover, the testsget to be compiled as other Rust kernel objects instead oftargeting userspace.On top of that, the integration with KUnit means the Rustsupport gets to reuse the existing testing facilities. Forinstance, the kernel log would look like: KTAP version 1 1..1 KTAP version 1 # Subtest: rust_doctests_kernel 1..59 # rust_doctest_kernel_build_assert_rs_0.location: rust/kernel/build_assert.rs:13 ok 1 rust_doctest_kernel_build_assert_rs_0 # rust_doctest_kernel_build_assert_rs_1.location: rust/kernel/build_assert.rs:56 ok 2 rust_doctest_kernel_build_assert_rs_1 # rust_doctest_kernel_init_rs_0.location: rust/kernel/init.rs:122 ok 3 rust_doctest_kernel_init_rs_0 ... # rust_doctest_kernel_types_rs_2.location: rust/kernel/types.rs:150 ok 59 rust_doctest_kernel_types_rs_2 # rust_doctests_kernel: pass:59 fail:0 skip:0 total:59 # Totals: pass:59 fail:0 skip:0 total:59 ok 1 rust_doctests_kernelTherefore, add support for running Rust documentation testsin KUnit. Some other notes about the current implementationand support follow.The transformation is performed by a couple scripts writtenas Rust hostprogs.Tests using the `?` operator are also supported as usual, e.g.: /// ``` /// # use kernel::{spawn_work_item, workqueue}; /// spawn_work_item!(workqueue::system(), || pr_info!("x"))?; /// # Ok::<(), Error>(()) /// ```The tests are also compiled with Clippy under `CLIPPY=1`, justlike normal code, thus also benefitting from extra linting.The names of the tests are currently automatically generated.This allows to reduce the burden for documentation writers,while keeping them fairly stable for bisection. This is animprovement over the `rustdoc`-generated names, which includethe line number; but ideally we would like to get `rustdoc` toprovide the Rust item path and a number (for multiple examplesin a single documented Rust item).In order for developers to easily see from which original linea failed doctests came from, a KTAP diagnostic line is printedto the log, containing the location (file and line) of theoriginal test (i.e. instead of the location in the generatedRust file): # rust_doctest_kernel_types_rs_2.location: rust/kernel/types.rs:150This line follows the syntax for declaring test metadata in theproposed KTAP v2 spec [1], which may be used for the proposedKUnit test attributes API [2]. Thus hopefully this will makemigration easier later on (suggested by David [3]).The original line in that test attribute is figured out byproviding an anchor (suggested by Boqun [4]). The original fileis found by walking the filesystem, checking directory prefixesto reduce the amount of combinations to check, and it is onlydone once per file. Ambiguities are detected and reported.A notable difference from KUnit C tests is that the Rust testsappear to assert using the usual `assert!` and `assert_eq!`macros from the Rust standard library (`core`). We providea custom version that forwards the call to KUnit instead.Importantly, these macros do not require passing context,unlike the KUnit C ones (i.e. `struct kunit *`). This makesthem easier to use, and readers of the documentation do not needto care about which testing framework is used. In addition, itmay allow us to test third-party code more easily in the future.However, a current limitation is that KUnit does not supportassertions in other tasks. Thus we presently simply print anerror to the kernel log if an assertion actually failed. Thisshould be revisited to properly fail the test, perhaps savingthe context somewhere else, or letting KUnit handle it.Link: https://lore.kernel.org/lkml/20230420205734.1288498-1-rmoar@google.com/ [1]Link: https://lore.kernel.org/linux-kselftest/20230707210947.1208717-1-rmoar@google.com/ [2]Link: https://lore.kernel.org/rust-for-linux/CABVgOSkOLO-8v6kdAGpmYnZUb+LKOX0CtYCo-Bge7r_2YTuXDQ@mail.gmail.com/ [3]Link: https://lore.kernel.org/rust-for-linux/ZIps86MbJF%2FiGIzd@boqun-archlinux/ [4]Signed-off-by: Miguel Ojeda Reviewed-by: David Gow Signed-off-by: Shuah Khan List of files: /linux-6.15/scripts/Makefile

05e96e96 - kbuild: use git-archive for source package creation

Wed, 15 Mar 2023 15:50:18 +0000

kbuild: use git-archive for source package creationCommit 5c3d1d0abb12 ("kbuild: add a tool to list files ignored by git")added a new tool, scripts/list-gitignored. My intention was to createsource packages without cleaning the source tree, without relying on git.Linus strongly objected to it, and suggested using 'git archive' instead.[1] [2] [3]This commit goes in that direction - Remove scripts/list-gitignored.cand rewrites Makefiles and scripts to use 'git archive' for buildingDebian and RPM source packages. It also makes 'make perf-tar*-src-pkg'use 'git archive' again.Going forward, building source packages is only possible in a git-managedtree. Building binary packages does not require git.[1]: https://lore.kernel.org/lkml/CAHk-=wi49sMaC7vY1yMagk7eqLK=1jHeHQ=yZ_k45P=xBccnmA@mail.gmail.com/[2]: https://lore.kernel.org/lkml/CAHk-=wh5AixGsLeT0qH2oZHKq0FLUTbyTw4qY921L=PwYgoGVw@mail.gmail.com/[3]: https://lore.kernel.org/lkml/CAHk-=wgM-W6Fu==EoAVCabxyX8eYBz9kNC88-tm9ExRQwA79UQ@mail.gmail.com/Fixes: 5c3d1d0abb12 ("kbuild: add a tool to list files ignored by git")Fixes: e0ca16749ac3 ("kbuild: make perf-tar*-src-pkg work without relying on git")Suggested-by: Linus Torvalds Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

5c3d1d0a - kbuild: add a tool to list files ignored by git

Wed, 15 Feb 2023 01:20:23 +0000

kbuild: add a tool to list files ignored by gitIn short, the motivation of this commit is to build a source packagewithout cleaning the source tree.The deb-pkg and (src)rpm-pkg targets first run 'make clean' beforecreating a source tarball. Otherwise build artifacts such as *.o,*.a, etc. would be included in the tarball. Yet, the tarball ends upcontaining several garbage files since 'make clean' does not cleaneverything.Cleaning the tree every time is annoying since it makes the incrementalbuild impossible. It is desirable to create a source tarball withoutcleaning the tree.In fact, there are some ways to achieve this.The easiest solution is 'git archive'. 'make perf-tar*-src-pkg' usesit, but I do not like it because it works only when the source tree ismanaged by git, and all files you want in the tarball must be committedin advance.I want to make it work without relying on git. We can do this.Files that are ignored by git are generated files, so should be excludedfrom the source tarball. We can list them out by parsing the .gitignorefiles. Of course, .gitignore does not cover all the cases, but it workswell enough.tar(1) claims to support it: --exclude-vcs-ignores Exclude files that match patterns read from VCS-specific ignore files. Supported files are: .cvsignore, .gitignore, .bzrignore, and .hgignore.The best scenario would be to use 'tar --exclude-vcs-ignores', but thisoption does not work. --exclude-vcs-ignore does not understand any ofthe negation (!), preceding slash, following slash, etc.. So, this optionis just useless.Hence, I wrote this gitignore parser. The previous version [1], writtenin Python, was so slow. This version is implemented in C, so it worksmuch faster.I imported the code from git (commit: 23c56f7bd5f1), so we get the sameresult.This tool traverses the source tree, parsing all .gitignore files, andprints file paths that are ignored by git.The output is similar to 'git ls-files --ignored --directory --others--exclude-per-directory=.gitignore', except [1] Not sorted [2] No trailing slash for directories[2] is intentional because tar's --exclude-from option cannot handletrailing slashes.[How to test this tool] $ git clean -dfx $ make -s -j$(nproc) defconfig all # or allmodconifg or whatever $ git archive -o ../linux1.tar --prefix=./ HEAD $ tar tf ../linux1.tar | LANG=C sort > ../file-list1 # files emitted by 'git archive' $ make scripts_package HOSTCC scripts/list-gitignored $ scripts/list-gitignored --prefix=./ -o ../exclude-list $ tar cf ../linux2.tar --exclude-from=../exclude-list . $ tar tf ../linux2.tar | LANG=C sort > ../file-list2 # files emitted by 'tar' $ diff ../file-list1 ../file-list2 | grep -E '^(<|>)' < ./Documentation/devicetree/bindings/.yamllint < ./drivers/clk/.kunitconfig < ./drivers/gpu/drm/tests/.kunitconfig < ./drivers/hid/.kunitconfig < ./fs/ext4/.kunitconfig < ./fs/fat/.kunitconfig < ./kernel/kcsan/.kunitconfig < ./lib/kunit/.kunitconfig < ./mm/kfence/.kunitconfig < ./tools/testing/selftests/arm64/tags/ < ./tools/testing/selftests/arm64/tags/.gitignore < ./tools/testing/selftests/arm64/tags/Makefile < ./tools/testing/selftests/arm64/tags/run_tags_test.sh < ./tools/testing/selftests/arm64/tags/tags_test.c < ./tools/testing/selftests/kvm/.gitignore < ./tools/testing/selftests/kvm/Makefile < ./tools/testing/selftests/kvm/config < ./tools/testing/selftests/kvm/settingsThe source tarball contains most of files that are tracked by git. Yousee some diffs, but it is just because some .gitignore files are wrong. $ git ls-files -i -c --exclude-per-directory=.gitignore Documentation/devicetree/bindings/.yamllint drivers/clk/.kunitconfig drivers/gpu/drm/tests/.kunitconfig drivers/hid/.kunitconfig fs/ext4/.kunitconfig fs/fat/.kunitconfig kernel/kcsan/.kunitconfig lib/kunit/.kunitconfig mm/kfence/.kunitconfig tools/testing/selftests/arm64/tags/.gitignore tools/testing/selftests/arm64/tags/Makefile tools/testing/selftests/arm64/tags/run_tags_test.sh tools/testing/selftests/arm64/tags/tags_test.c tools/testing/selftests/kvm/.gitignore tools/testing/selftests/kvm/Makefile tools/testing/selftests/kvm/config tools/testing/selftests/kvm/settings[1]: https://lore.kernel.org/all/20230128173843.765212-1-masahiroy@kernel.org/Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

ec61452a - scripts: remove bin2c

Thu, 19 Jan 2023 07:12:15 +0000

scripts: remove bin2cCommit 80f8be7af03f ("tomoyo: Omit use of bin2c") removed the lastuse of bin2c.Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier Reviewed-by: Sedat Dilek List of files: /linux-6.15/scripts/Makefile

c83b16ce - kbuild: rust: move rust/target.json to scripts/

Sat, 07 Jan 2023 09:45:45 +0000

kbuild: rust: move rust/target.json to scripts/scripts/ is a better place to generate files used treewide.With target.json moved to scripts/, you do not need to add target.jsonto no-clean-files or MRPROPER_FILES.'make clean' does not visit scripts/, but 'make mrproper' does.Signed-off-by: Masahiro Yamada Reviewed-by: Miguel Ojeda Tested-by: Miguel Ojeda List of files: /linux-6.15/scripts/Makefile

2f7ab126 - Kbuild: add Rust support

Sat, 03 Jul 2021 14:42:57 +0000

Kbuild: add Rust supportHaving most of the new files in place, we now enable Rust supportin the build system, including `Kconfig` entries related to Rust,the Rust configuration printer and a few other bits.Reviewed-by: Kees Cook Reviewed-by: Nick Desaulniers Tested-by: Nick Desaulniers Reviewed-by: Greg Kroah-Hartman Co-developed-by: Alex Gaynor Signed-off-by: Alex Gaynor Co-developed-by: Finn Behrens Signed-off-by: Finn Behrens Co-developed-by: Adam Bratschi-Kaye Signed-off-by: Adam Bratschi-Kaye Co-developed-by: Wedson Almeida Filho Signed-off-by: Wedson Almeida Filho Co-developed-by: Michael Ellerman Signed-off-by: Michael Ellerman Co-developed-by: Sven Van Asbroeck Signed-off-by: Sven Van Asbroeck Co-developed-by: Gary Guo Signed-off-by: Gary Guo Co-developed-by: Boris-Chengbiao Zhou Signed-off-by: Boris-Chengbiao Zhou Co-developed-by: Boqun Feng Signed-off-by: Boqun Feng Co-developed-by: Douglas Su Signed-off-by: Douglas Su Co-developed-by: Dariusz Sosnowski Signed-off-by: Dariusz Sosnowski Co-developed-by: Antonio Terceiro Signed-off-by: Antonio Terceiro Co-developed-by: Daniel Xu Signed-off-by: Daniel Xu Co-developed-by: Björn Roy Baron Signed-off-by: Björn Roy Baron Co-developed-by: Martin Rodriguez Reboredo Signed-off-by: Martin Rodriguez Reboredo Signed-off-by: Miguel Ojeda List of files: /linux-6.15/scripts/Makefile

d5ea4fec - kbuild: Allow kernel installation packaging to override pkg-config

Fri, 01 Apr 2022 23:18:02 +0000

kbuild: Allow kernel installation packaging to override pkg-configAdd HOSTPKG_CONFIG to allow tooling that builds the kernel to overridewhat pkg-config and parameters are used.Signed-off-by: Chun-Tse Shao Reviewed-by: Nick Desaulniers Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

4ed308c4 - ftrace: Have architectures opt-in for mcount build time sorting

Tue, 25 Jan 2022 14:19:10 +0000

ftrace: Have architectures opt-in for mcount build time sortingFirst S390 complained that the sorting of the mcount sections at buildtime caused the kernel to crash on their architecture. Now PowerPC iscomplaining about it too. And also ARM64 appears to be having issues.It may be necessary to also update the relocation table for the valuesin the mcount table. Not only do we have to sort the table, but alsoupdate the relocations that may be applied to the items in the table.If the system is not relocatable, then it is fine to sort, but if it is,some architectures may have issues (although x86 does not as it shifts alladdresses the same).Add a HAVE_BUILDTIME_MCOUNT_SORT that an architecture can set to say it issafe to do the sorting at build time.Also update the config to compile in build time sorting in the sorttablecode in scripts/ to depend on CONFIG_BUILDTIME_MCOUNT_SORT.Link: https://lore.kernel.org/all/944D10DA-8200-4BA9-8D0A-3BED9AA99F82@linux.ibm.com/Link: https://lkml.kernel.org/r/20220127153821.3bc1ac6e@gandalf.local.homeCc: Ingo Molnar Cc: Andrew Morton Cc: Russell King Cc: Yinan Liu Cc: Ard Biesheuvel Cc: Kees Cook Reported-by: Sachin Sant Reviewed-by: Mark Rutland Tested-by: Mark Rutland [arm64]Tested-by: Sachin Sant Fixes: 72b3942a173c ("scripts: ftrace - move the sort-processing in ftrace_init")Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/scripts/Makefile

72b3942a - scripts: ftrace - move the sort-processing in ftrace_init

Sun, 12 Dec 2021 11:33:58 +0000

scripts: ftrace - move the sort-processing in ftrace_initWhen the kernel starts, the initialization of ftrace takesup a portion of the time (approximately 6~8ms) to sort mcountaddresses. We can save this time by moving mcount-sorting tocompile time.Link: https://lkml.kernel.org/r/20211212113358.34208-2-yinan@linux.alibaba.comSigned-off-by: Yinan Liu Reported-by: kernel test robot Reported-by: kernel test robot Signed-off-by: Steven Rostedt List of files: /linux-6.15/scripts/Makefile

340a0253 - certs: move scripts/extract-cert to certs/

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

certs: move scripts/extract-cert to certs/extract-cert is only used in certs/Makefile.Move it there and build extract-cert on demand.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile

d1f04410 - certs: Add ability to preload revocation certs

Fri, 22 Jan 2021 18:10:53 +0000

certs: Add ability to preload revocation certsAdd a new Kconfig option called SYSTEM_REVOCATION_KEYS. If set,this option should be the filename of a PEM-formated file containingX.509 certificates to be included in the default blacklist keyring.DH Changes: - Make the new Kconfig option depend on SYSTEM_REVOCATION_LIST. - Fix SYSTEM_REVOCATION_KEYS=n, but CONFIG_SYSTEM_REVOCATION_LIST=y[1][2]. - Use CONFIG_SYSTEM_REVOCATION_LIST for extract-cert[3]. - Use CONFIG_SYSTEM_REVOCATION_LIST for revocation_certificates.o[3].Signed-off-by: Eric Snowberg Acked-by: Jarkko Sakkinen Signed-off-by: David Howells cc: Randy Dunlap cc: keyrings@vger.kernel.orgLink: https://lore.kernel.org/r/e1c15c74-82ce-3a69-44de-a33af9b320ea@infradead.org/ [1]Link: https://lore.kernel.org/r/20210303034418.106762-1-eric.snowberg@oracle.com/ [2]Link: https://lore.kernel.org/r/20210304175030.184131-1-eric.snowberg@oracle.com/ [3]Link: https://lore.kernel.org/r/20200930201508.35113-3-eric.snowberg@oracle.com/Link: https://lore.kernel.org/r/20210122181054.32635-4-eric.snowberg@oracle.com/ # v5Link: https://lore.kernel.org/r/161428673564.677100.4112098280028451629.stgit@warthog.procyon.org.uk/Link: https://lore.kernel.org/r/161433312452.902181.4146169951896577982.stgit@warthog.procyon.org.uk/ # v2Link: https://lore.kernel.org/r/161529606657.163428.3340689182456495390.stgit@warthog.procyon.org.uk/ # v3 List of files: /linux-6.15/scripts/Makefile

fe968c41 - scripts: set proper OpenSSL include dir also for sign-file

Fri, 12 Feb 2021 07:22:27 +0000

scripts: set proper OpenSSL include dir also for sign-fileFixes: 2cea4a7a1885 ("scripts: use pkg-config to locate libcrypto")Signed-off-by: Rolf Eike Beer Cc: stable@vger.kernel.org # 5.6.xSigned-off-by: Masahiro Yamada List of files: /linux-6.15/scripts/Makefile