linux/poky.git/meta/recipes-kernel/kern-tools, branch master-next

kern-tools: fix symbol_why for v6.18-rc1+

2025-10-19T14:35:06+00:00

commit f589e1df23251d8319063da0a61c1016b2a0bf85 (HEAD -> master) Author: Bruce Ashfield Date: Wed Oct 15 18:12:20 2025 -0400 tools/Kconfiglib: add support for transitional attribute We need to update the parser to handle: commit f9afce4f32e9a120fc902fa6c9e0b90ad799a6ec Author: Kees Cook Date: Tue Sep 23 14:34:18 2025 -0700 kconfig: Add transitional symbol attribute for migration support During kernel option migrations (e.g. CONFIG_CFI_CLANG to CONFIG_CFI), existing .config files need to maintain backward compatibility while preventing deprecated options from appearing in newly generated configurations. This is challenging with existing Kconfig mechanisms because: 1. Simply removing old options breaks existing .config files. 2. Manually listing an option as "deprecated" leaves it needlessly visible and still writes them to new .config files. 3. Using any method to remove visibility (.e.g no 'prompt', 'if n', etc) prevents the option from being processed at all. Add a "transitional" attribute that creates symbols which are: - Processed during configuration (can influence other symbols' defaults) - Hidden from user menus (no prompts appear) - Omitted from newly written .config files (gets migrated) - Restricted to only having help sections (no defaults, selects, etc) making it truly just a "prior value pass-through" option. The transitional syntax requires a type argument and prevents type redefinition: config NEW_OPTION bool "New option" default OLD_OPTION config OLD_OPTION bool transitional help Transitional config for OLD_OPTION migration. This allows seamless migration: olddefconfig processes existing CONFIG_OLD_OPTION=y settings to enable CONFIG_NEW_OPTION=y, while CONFIG_OLD_OPTION is omitted from newly generated .config files. Added positive and negative testing via "testconfig" make target. Co-developed-by: Vegard Nossum Signed-off-by: Vegard Nossum Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor Link: https://lore.kernel.org/r/20250923213422.1105654-2-kees@kernel.org Signed-off-by: Kees Cook (From OE-Core rev: 8306d2bdcc48718aaa35dfa56b5364d90ea2a1db) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

meta: remove S in recipes that fetch from git via setting BB_GIT_DEFAULT_DESTSUFFIX

2025-06-20T11:07:26+00:00

Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). A few recipes are setting S to a sub-directory of the git tree and need to be adjusted accordingly. bzip2 recipe is fetching a tarball and separately cloning tests; adjust the recipe to put the latter into 'bzip2-tests', instead of 'git'. devupstream.bbclass no longer needs to rewrite S, and is adjusted accordingly. Adjust scripts/lib/recipetool/append.py to not hardcode 'git' as unpack destination. Adjust kernel-yocto.bbclass to use the git unpack variable instead of hardcoding 'git' (there's also removal of repetition of string constants and a correction of workdir/unpackdir mismatch in one of the if-else branches). Ensure build-appliance-image recipe does not use 'git' as checkout directory for poky repo, but rather explicitly name it 'poky'. Ensure reproducible.py code that looks for git repositories does not hardcode 'git' but uses the destination set by BB_GIT_DEFAULT_DESTSUFFIX. Ensure recipetool does not write out unneeded S settings into newly created recipes that fetch from git. Adjust selftest to not hardcode 'git' as unpack directory. (From OE-Core rev: f80c07019ddadaf9c5fb890faabfda7920ecd15e) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

kernel-yocto: allow annotated options to be modified

2025-05-08T22:16:54+00:00

Bumping the kern-tools SRCREV to pickup the following commits: tools: allow fixups to conditionally change options Sometimes we have options that should either be =y or =m depending on the use case. Rather than force the options into multiple parallel and very similar fragments (which is error prone and labour intensive), we can allow an annotation in the configuration fragment that allows the default value to be overriden by a variable. The variable in question comes from a -D= on the scc or spp command line. If the define evaluates to a non-zero value a fixup is created that will modify the value when scc finishes gathering meta-data. An example of a notation would be: CONFIG_INET_TUNNEL=y # OVERRIDE:$MODULE_OR_Y CONFIG_INET_TUNNEL will be =y when standard tools (like merge-config) are used. But when scc/spp see this notation, they check the value of the variable MODULE_OR_Y, if that variable evalutes to a non-zero value, a fixup is created that will change CONFIG_INET_TUNNEL to that value before the kernel is configured. To use the annotations, scc needs to be passed a value that is used in the override expression. This has always been possible with defines (-Dx=y), so we leverage that to control these conditional overrides. In kernel-yocto, we now have a variable: KMETA_CONFIG_FEATURES KMETA_CONFIG_FEATURES ?= "" Which defaults to empty, the only feature that is currently implemented is "prefer-modules". When prefer-modules is detected in the kmeta config features, the following define is passed to scc: -DMODULE_OR_Y=m Which as you can see from the above INET_TUNNEL example, will evaluate to "m" and will override the default of "y". (From OE-Core rev: 4eb24e85e815cee0e310e98ce4384d4cdeeba69f) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: allow comments after configuration options

2025-04-11T09:41:05+00:00

Bumping the kern-tools SRCREV to allow comments after configuration options. Without this update of the regex, symbol_why will incorrectly detect that options are not in the final .config during audit. (From OE-Core rev: ccfdd07adbfda1e3892a54706c610cdeab83237b) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: fix python 3.12 warning

2025-01-04T12:34:04+00:00

Integrating the following commit: Author: hongxu Date: Tue Dec 17 01:47:19 2024 -0800 symbol_why: fix SyntaxWarning for RegEx calls on Python 3.12 Python 3.12 emmits a SyntaxWarning when using unescaped character inside a RegEx string. ''' recipe-sysroot-native/usr/bin/symbol_why.py:161: SyntaxWarning: invalid escape sequence '\.' if re.match( ".*\.config", opt ): recipe-sysroot-native/usr/bin/symbol_why.py:216: SyntaxWarning: invalid escape sequence '\w' x = re.match( "^# .*Linux/\w*\s*([0-9]*\.[0-9]*\.[0-9]*).*Kernel Configuration", line ) recipe-sysroot-native/usr/bin/symbol_why.py:495: SyntaxWarning: invalid escape sequence '\s' if re.search( "^#\s*CONFIG_", option ): ''' According to [1], use raw strings for regular expression [1] https://docs.python.org/dev/whatsnew/3.12.html#other-language-changes Signed-off-by: Hongxu Jia (From OE-Core rev: 18d60c209364f01f183000de8640f6f40496e922) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: allow inputs to be tagged for audit

2024-11-07T13:31:26+00:00

Integrating the following commit: Author: Bruce Ashfield Date: Wed Oct 16 23:34:04 2024 -0400 spp: allow inputs to be tagged for audit files can have a specifier "optional" or "required" which follows the input file and is separated by a : We need to adjust our routines to check for the specifier and split it out accordingly. (From OE-Core rev: d5881f4cf09f82b31e731fafa96ab9ad5f55b17d) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: allow .config to be recognized as a fragment

2024-11-07T13:31:26+00:00

Integrating the following commit: Author: Paul Barker Date: Wed Oct 2 10:01:29 2024 +0000 spp: Allow .config extension for config fragments The config fragments present in the upstream Linux kernel use the .config extension, for example arch/riscv/configs/32-bit.config or kernel/configs/hardening.config. To allow these to be easily used without having to copy or rename them, extend spp to support both .cfg and .config file extensions. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield (From OE-Core rev: 99e51028331ee80ac8b55652ab895636b8b39979) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: depend on git-replacement-native

2024-02-27T14:31:36+00:00

Konstantin Aladyshev reported that the kern-tools require git functionality that was introduced in git versions greater than the minimum project requirements. In particular: commit 923a9de418b3ca8592c3 [kgit-s2q: don't run verication hooks] uses the --no-verify flag to prevent local git hooks from running and breaking patching or introducing security issues from the host configuration. To ensure that we have a new enough git available for the tools, we update our DEPENDS to git-native-replacement, and the version available in oe-core will be built and used instead of the host provided version. (From OE-Core rev: 6c2ae2346db061a37506b3b5dca20914a7b29fca) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: update SRCREV to include SECURITY.md file

2023-11-09T16:57:26+00:00

To be compliant with the recent security policy, bumping the SRCREV to pickup the SECUIRTY.md of the kern-tools repository. It's contents are repeated below: How to Report a Potential Vulnerability? ======================================== If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla]. If you have a patch ready, submit it following the same procedure as any other patch as described in README.md. If you are dealing with a not-yet released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available. Branches maintained with security fixes --------------------------------------- See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS] for detailed info regarding the policies and maintenance of Stable branches. The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues. (From OE-Core rev: fbdfc28b290ea3ed2dc3dbbaf461adc2839eb8f2) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: bump SRCREV for queue processing changes

2023-11-09T16:57:26+00:00

Bumping the SRCREV to pickup a new option to the patch and merge queue handling scripts. The new option '--prev' allows us to change the behaviour of a subsequent runs to retry a failed patch, versus skipping it. (From OE-Core rev: 231256485ae528773a4da9fad8bf4baff26fc0d2) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie