summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: cooker: adjust the error message about missing websockets module to ↵Alexander Kanavin2025-10-031-1/+4
| | | | | | | | | mention bitbake-setup (Bitbake rev: d857ed2044c8153c69bd3e275cfc8a9b6a8cdc5e) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add 'install-buildtools' commandAlexander Kanavin2025-10-032-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This basically calls install-buildtools from oe-core/poky, but it ensures via command line parameters that the installation location is stable and the downloads are preserved for reproducibility: $ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf ====== Buildtools archive is downloaded into /home/alex/bitbake-builds/yocto-master-testing/buildtools-downloads/20250319141333 and its content installed into /home/alex/bitbake-builds/yocto-master-testing/buildtools ... (output from install-buildtools script) ====== It also detects when buildtools are already installed, and will direct users what to do: ====== alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf Buildtools are already installed in /home/alex/bitbake-builds/yocto-master-testing/buildtools. If you wish to use them, you need to source the the environment setup script e.g. $ . /home/alex/bitbake-builds/yocto-master-testing/buildtools/environment-setup-x86_64-pokysdk-linux You can also re-run bitbake-setup install-buildtools with --force option to force a reinstallation ====== This commits includes fixes by Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 (Bitbake rev: 9fb564b720ff5d29a245ec900c8996da7f5f24a6) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add tests to bitbake-selftestAlexander Kanavin2025-10-032-0/+267
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Run like this: alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-selftest -v bb.tests.setup test_setup (bb.tests.setup.BitbakeSetupTest.test_setup) ... ok ---------------------------------------------------------------------- Ran 1 test in 9.223s OK The test does a basic run-through of init, then status/update on an unchanged configuration, then status/update on a configuration changed via new commits to the test layer, then status/update on configuration changed via the top level json config file. Note that nothing whatsoever is fetched from the network; the test relies entirely on synthetic data contained inside itself, including minimal stubs for oe-setup-build and bitbake-config-build. This data is used to create temporary git repositories then clone them via local filesystem URIs. Later on this can be supplemented by an oe-selftest that tests bitbake-setup against real config files in the official configuration repository and real layers, templates and fragments. (Bitbake rev: 59ec7e2ac56e364bae39ccb5e884c447a5379531) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add the initial implementationAlexander Kanavin2025-10-031-0/+809
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Preamble ======== The latest iteration of this patchset is available at https://github.com/kanavin/bitbake I recommend taking the patches from there to ensure that you are not trying out outdated code. For the rationale and design guidelines please see this message: https://lists.openembedded.org/g/openembedded-architecture/message/1913 Left out for now but will be done later: - official configuration repository - documentation Amble *scratch* HOWTO ===================== 1. If you don't know where to start, run 'bitbake-setup init'. Bitbake-setup will ask a few questions about available configuration choices and set up a build. Note: 'init' sub-command can also take a path or a URL with a configuration file directly. You can see how those files look like here: https://github.com/kanavin/bitbake-setup-configurations 2. You can then source the bitbake environment and run bitbake to perform builds as usual: $ . /home/alex/bitbake-builds/yocto-master-options-poky-distro_poky-machine_qemux86-64/build/init-build-env Also, subsequent status/update commands will not require a separate --build-dir argument telling bitbake-setup where the build is. 3. To check if the build configuration needs to be updated, run: === $ bin/bitbake-setup status ... Configuration in /home/alex/bitbake-builds/poky-alex/ has not changed. === If the configuration has changed, you will see the difference as a diff. ... - "rev": "akanavin/sstate-for-all" + "rev": "akanavin/bitbake-setup-testing" ... If the configuration has not changed, but layer revisions referred to it have (for example if the configuration specifies a tip of a branch), you will see that too: === ... Layer repository git://git.yoctoproject.org/poky-contrib checked out into /home/alex/builds/poky-alex/layers/poky updated revision akanavin/sstate-for-all from 6b842ba55f996b27c900e3de78ceac8cb3b1c492 to aeb73e29379fe6007a8adc8d94c1ac18a93e68de === 4. If the configuration has changed, you can bring it in sync with: $ bin/bitbake-setup update Note that it will also rename/preserve the existing build/conf directory, and print changes in bitbake configuration (diff of content of build/conf/) if that has changed. I can't at the moment think of anything more clever that is also not much more brittle or complex to implement, but open to suggestions. Terminology =========== - 'top directory' means the place under which bitbake-setup reads and writes everything. bitbake-setup makes a promise to not touch anything outside of that, unless otherwise directed to by entries in settings (currently there is one such setting for fetcher downloads for layers and config registries). Top directory can be selected by an environment variable, a command line option, or otherwise assumed to be ~/bitbake-builds/. If BBPATH is in environment (e.g. we are in a bitbake environment), then the top directory is deduced from that and doesn't need to be specified by hand. - 'settings' means bitbake-setup operational parameters that are global to all builds under a top directory. E.g. the location of configuration registry, or where the bitbake fetcher should place the downloads (DL_DIR setting). Settings are stored in a .conf file in ini format just under the top directory. - 'build' means a tree structure set up by 'bitbake-setup init', consisting of, at least, a layers checkout, and a bitbake build. It maps 1:1 to the json data it was constructed from, which is called 'build configuration'. Build configurations are constructed from generic configurations that may involve making one or more choices about available options in them. Generic configurations are files, URLs or are obtained from git repositories called 'config registries', in which case they can be listed with 'bitbake-setup list'. There can be multiple 'builds' under a top directory. Here are two example generic configurations that showcase this: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-options.conf.json https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-nested-configs.conf.json - 'bitbake-setup status' will tell if a build is in sync with the generic configuration it was made from. 'bitbake-setup update' will bring a build in sync with a configuration if needed. - 'bitbake build' means a particular sub-tree inside a build that bitbake itself operates on, e.g. what is set in BBPATH/BUILDDIR by oe-init-build-env. conf/* in that tree is 'bitbake configuration'. Bitbake configurations are constructed from templates and fragments, with existing mechanisms provided by oe-core. The configuration file format is specified such that other mechanisms to set up a bitbake build can be added; there was a mention of ability to specify local.conf content and a set of layers directly in a configuration. I think that scales poorly compared to templates and fragments, but I made sure alternative ways to configure a bitbake build are possible to add in the future :) - 'source override' is a json file that can be used to modify revisions and origins of layers that need to be checkout into a build (e.g. when master branches need to be changed to master-next for purposes of testing). Such a file is specified with a command-line option to 'init' and an example can be seen here: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-next.override.json This commit includes fixes by Ryan Eatmon <reatmon@ti.com> https://github.com/kanavin/bitbake/pull/1 Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 Johannes Schneider <johannes.schneider@leica-geosystems.com> https://github.com/kanavin/bitbake/pull/3 https://github.com/kanavin/bitbake/pull/5 (Bitbake rev: bf3542076cdd751da9de8745aa3f351f5c6b0c5f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse: Make include_all raise a parse error for absolute pathsPeter Kjellerstedt2025-10-032-0/+4
| | | | | | | | | It makes no sense to use an absolute path with include_all. (Bitbake rev: a39d1d5df740824d40c4d8e7f4199ccc518592e0) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse: Make include_all support empty variable expansionsPeter Kjellerstedt2025-10-033-5/+9
| | | | | | | | | | | | | include and require support empty variable expansions, typically used with conditional expansions. However, include_all does not, and instead reports an error for the first path in BBPATH. Rewrite include_all so that its behavior matches include and require. (Bitbake rev: 010928ceac48b20e6ab530f8e256b72201b778ec) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: do not require CONF_VERSION (e.g. local.conf version) to ↵Alexander Kanavin2025-10-021-1/+7
| | | | | | | | | | | | | | | | | | be set The version checks for local.conf/site.conf/bblayers.conf are all optional, and aren't enforced (by insane class) if the versions aren't set. As bitbake-setup writes out a blank local.conf, it doesn't put a version in it either. Also, esdk bundle has a fixed set of layers and is not at risk of needing to update its own local.conf. The same condition is already in place for esdk's bblayers.conf for similar reasons. (From OE-Core rev: d83ff28157aaa9322f98b8da5dd50b562085085a) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ghostscript: upgrade 10.05.1 -> 10.06.0Vijay Anusuri2025-10-023-70/+66
| | | | | | | | | | | | | | | | | | | | Dropped 0001-Bug-708160-Fix-compatibility-with-C23-compilers.patch Added 0001-Fix-32-bit-build.patch to fix 32-bit archs build Added fPIC flag needed to prevent a linker error during the build process. This upgrade addresses CVEs: CVE-2025-59798, CVE-2025-59799, CVE-2025-59800, CVE-2025-59801 Changelog: https://ghostscript.readthedocs.io/en/gs10.06.0/News.html (From OE-Core rev: 0144e22195394ce2b21b476a1dcfde9129eaf615) Signed-off-by: Vijay Anusuri <vanusuri@mvista.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.py: replace all files unconditionally when copy debug sourcesChangqing Li2025-10-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is for fixing reproducible issue for package like: intel-speed-select-src. For intel-speed-select, one of the debug sources is /usr/src/debug/intel-speed-select/1.0/include/linux/thermal.h, file include/linux/thermal.h under ${S} (kernel-sources) link file include/linux/thermal.h under ${B}, which link to ${S}/include/uapi/linux/thermal.h During copy debug sources, sources under ${S} copied first, then sources under ${B} is copied. mtime of ${S}/include/linux/thermal.h and ${S}/include/uapi/linux/thermal.h are decided by when it is fetched, so it is not determinate, maybe same or different. For cpio, if the in file is older than or the same as the exist file, cpio will not replace the exist file with warning "cpio: xxx not created: newer or same age version exists". And this will cause intel-speed-select-src maybe not reproducible. And option '-u' for cpio, first, this will make the copied file determistic. Second, source files under ${B} should have higher priority then ${S}, it may be generated during build, the target is more likely to use this file. (From OE-Core rev: 8898f97b4acc9d5c2c6583c91d05327f9093133e) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Fix FILES for intel firmwareRyan Eatmon2025-10-021-26/+26
| | | | | | | | | | | | | | | | The 20250917 version is installing the firmware files into the /usr/lib/firmware/intel directory and symbolic links to those files under /usr/lib/firmware. FILES needs to be updated to correctly package all of the files into the right packages. Without this we get a dependency from the linux-firmware-iwlwifi-* and linux-firmware-qat packages back to linux-firmware which means you have to install ALL of the drivers when you depend on the specific package. (From OE-Core rev: d5144f7031f1f25bb769aed860c45b1fe00ddba4) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: build with MinSizeRelRoss Burton2025-10-021-3/+3
| | | | | | | | | | | | | | | | | | | This is the recommended build configuration upstream unless speed is the ultimate goal. They say it's almost as fast as Release (-O3) but a lot smaller on disk: clang-libclang-cpp: PKGSIZE changed from 71729568 to 49368816 (-31%) clang-libllvm: PKGSIZE changed from 83015559 to 56662823 (-32%) clang-tidy: PKGSIZE changed from 15861679 to 9956175 (-37%) clang-tools: PKGSIZE changed from 6865635 to 5374691 (-22%) clang: PKGSIZE changed from 29693308 to 22697548 (-24%) libclang: PKGSIZE changed from 40087018 to 26966218 (-33%) (From OE-Core rev: ea9b33f7c12f773830ec860ae817a3ed1368612b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: fix reproducibility issue in LLVMConfig.cmakeRoss Burton2025-10-022-0/+30
| | | | | | | | | | | | | | | | | | | The LLVMConfig.cmake file is mostly LLVM configuration, but it also specifies if some Python modules (needed by the opt-viewer tool) were present on the build host. This is host contamination and a source of non-determinism, so remove it from the installed file. A ticket has been filed upstream to resolve this: https://github.com/llvm/llvm-project/issues/161199 (From OE-Core rev: 916c074a136e8e07f388c2c41d197a15a4c50022) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: use EXTRA_OECMAKE +=Ross Burton2025-10-023-13/+13
| | | | | | | | | | Don't assign EXTRA_OECMAKE so that the include files can set defaults. (From OE-Core rev: 5ad8d6ddf7a1ada37ad1070a3d3347c7f6d57148) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gn: Add recipeKhem Raj2025-10-023-0/+54
| | | | | | | | | | | | | | | | | | | | | | | gn is a commonly used build tool to generate ninja files, used in a lot of recipes e.g. chromium, qtwebengine, perfetto, hafnium etc. these recipes come from different layers e.g. meta-qt6/meta-arm/meta-oe since not all layers depend on meta-oe ( meta-arm does not ), its not a possible option. Given the usecases, putting it in core will benefit the ecosystem and reduce some duplication. This recipe is taken from meta-arm Disable maybe-initialized is a gcc specific option as error Disable format warnings as errors, it adds -Wno-format explictly in its build system (From OE-Core rev: e8dbf41f1f40ae3a5f9641429cad974f716f1f3e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Update to tip of trunkKhem Raj2025-10-021-1/+1
| | | | | | | | | | | | | | Brings * 0ccaf057 printf: fix buffer overflow in floating point decimal formatting * 0b86d60b riscv: fix setjmp assembly when compiling for ilp32f/lp64f. * f6944eb3 powerpc[64]: fix missing ctr and xer regs in syscall asm clobberlists * a6244de1 fix erroneous definition of IN6_IS_ADDR_V4COMPAT (From OE-Core rev: 9ba3fbf1d4ed63b22d108d4d2beebcbcfa352884) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-c: update 0.10.15 -> 0.10.16Deepesh Varatharajan2025-10-022-293/+283
| | | | | | | | (From OE-Core rev: d3cf1b37ce8686dc0781aff9bf35f4487c2c76a6) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Update minimum gcc version to 10.1Antonin Godard2025-10-021-6/+3
| | | | | | | | | | | | | | | | | | | Since commit 19004950ad56 ("sanity: Check if the C++ toolchain supports --std=gnu++20") host GCC must support "--std=gnu++20", which became available in 10.1. This is already reflected in the documentation [1] but not here. Update the sanity check on GCC and raise the minimum version to 10.1. Remove the dead link to www.softwarecollections.org. [1]: https://git.yoctoproject.org/yocto-docs/commit/?id=0e538c102bfcb7184c76c2401e8cb878168c4434 Cc: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 871cc04305fe7483a4c256f38fa63a67cef82183) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: backport the topology rename patchDmitry Baryshkov2025-10-022-1/+41
| | | | | | | | | | | | Backport the patch from the trunk, renaming topology file for one of Qualcomm boards in order to reduce possible compatibility issues. Cc: Vivek Puar <vpuar@qti.qualcomm.com> (From OE-Core rev: ee1600aff7ed3c18f5cb512ca069ff564063744e) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: fix Bluetooth LE audio regressionGuðni Már Gilbert2025-10-022-0/+30
| | | | | | | | | | Backport a fix for a regression introduced in 5.84 which breaks Bluetooth LE audio (From OE-Core rev: 2b675c5cbfcaa7a5918ddd4a13400be5be60b3e6) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: Increase the maximum group name length to 32 (the default)Peter Kjellerstedt2025-10-021-1/+0
| | | | | | | | | | | | | | | Back in 2014, the maximum group name length was increased from 16 (the default) to 24. Since then, the default has increased to 32, and our configuration is now actually a decrease in maximum group name length. Remove the configuration to use the default instead, which aligns the maximum group name length with the maximum user name length. (From OE-Core rev: 02c98c3b199bfe3c6b8acd6e2ebf13088564c351) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: upgrade to 1.9.1Ross Burton2025-10-026-103/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes in this release: 751b09390 Bump versions to 1.9.1 for release d0abb2133 Boost python must have a library component. e6732c220 Check for header only Boost libraries. 08429813b get_llvm_tool_names: add llvm 21 f3b383217 docs: fix pre-1.8 order for per-subproject options a2d395498 Revert "test cases: do not pass global option on command line" d0f82544e Revert "tests: skip test common/223 in the -Ddefault_library=... jobs" 2abdb2f0b options: put back in place 1.7 ordering of opt=value vs subp:opt=value 83cbc65c2 Fix not passing user option args to scan-build build e746db0b4 Document internal dep support in pkgconfig.generate `requires` arg f6ab732b7 msetup: not-found subprojects do not have known options 5d21e653a utils: make .wraplock optional d1e219cb8 Fix Cygwin test failure. 0fc77e2d7 coredata: do not write None to cmd_line.txt 533ba5cb3 options: do not raise exception for unknown options in -U command ae822d1d4 test cases/common/32 has header: disable undef with libcxx c58f0d951 rustdoc: skip --crate-type option b8e0e9d3d fix transient failure on rust/12 bindgen 75cf757b7 coredata: check for per-subproject compiler and linker arguments a747c4ea8 coredata: check for per-subproject compiler options Drop the two backported patches. (From OE-Core rev: 3acddf6cae1449591227b2f07fed13195cad0b82) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xkeyboard-config: Turn absolute symlinks into relativeKhem Raj2025-10-021-1/+1
| | | | | | | | | | | | | | | | | | | Native builds encode symlinks pointing to absolute paths into build native sysroot which gets into sstate artifacts and an error is rightly generated ERROR: xkeyboard-config-native-2.45-r0 do_populate_sysroot: sstate found an absolute path symlink /mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/sysroot-destdir/mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/recipe-sysroot-native/usr/share/X11/xkb pointing at /mnt/b/yoe/master/build/tmp/work/x86_64-linux/xkeyboard-config-native/2.45/recipe-sysroot-native/usr/share/xkeyboard-config-2. Please replace this with a relative link. ERROR: xkeyboard-config-native-2.45-r0 do_populate_sysroot: Failing task due to absolute path symlinks Turn these symlinks to be relative inside D which will reflect correclty without need for absolute path prefix Suggested-by: Zoltán Böszörményi <zboszor@gmail.com> (From OE-Core rev: 811d4a9186c520e860877da536f5544daac9a2a9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2025-10-011-1/+1
| | | | | | (From OE-Core rev: 9f1a1fc1a163e74602d8a359483087f1117f23c2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: Update SANITY_TESTED_DISTROSRichard Purdie2025-10-011-1/+3
| | | | | | | | Add Fedora 52, Debian 13 and Ubuntu 25.04, drop Ubuntu 24.10. (From meta-yocto rev: 837a650aac17598dd2b0113f47c9058f2162cd34) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-target-config: Update the data layout for ppc64 targets.Deepesh Varatharajan2025-10-011-2/+2
| | | | | | | | | | | Rust commit for updating the data layouts: https://github.com/rust-lang/rust/commit/0680155a171d47772302fc4da4cbbfa466378d81 (From OE-Core rev: cf1972b7b96bb38b48e90654a8c840568e4646cf) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: update CVE exclusions (6.12.49)Bruce Ashfield2025-10-011-8/+56
| | | | | | | | | | | | | | | | | | Data pulled from: https://github.com/CVEProject/cvelistV5 1/1 [ Author: cvelistV5 Github Action Email: github_action@example.com Subject: 1 changes (1 new | 0 updated): - 1 new CVEs: CVE-2025-11135 - 0 updated CVEs: Date: Mon, 29 Sep 2025 01:40:51 +0000 ] (From OE-Core rev: 13acb9570660dde8f1cccb045981b646acb44aea) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.12: update to v6.12.49Bruce Ashfield2025-10-013-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating linux-yocto/6.12 to the latest korg -stable release that comprises the following commits: da274362a7bd Linux 6.12.49 6553fdf0f7d4 minmax.h: remove some #defines that are only expanded once cf5fe0b36f10 minmax.h: simplify the variants of clamp() 5c2b06b31da6 minmax.h: move all the clamp() definitions after the min/max() ones 5f6818002047 minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() e94ce277b568 minmax.h: reduce the #define expansion of min(), max() and clamp() ab58f71b8fdf minmax.h: update some comments d9c5ccf6b69b minmax.h: add whitespace around operators and after commas 63fd831aa5dc rtc: pcf2127: fix SPI command byte for PCF2131 backport 207fa0d49522 xhci: dbc: Fix full DbC transfer ring after several reconnects 490f1ca013b5 xhci: dbc: decouple endpoint allocation from initialization 9b28ef1e4cc0 usb: xhci: remove option to change a default ring's TRB cycle bit e5051c055926 usb: xhci: introduce macro for ring segment list iteration c839be6df4da mptcp: pm: nl: announce deny-join-id0 flag 34f351c0fa95 mm/gup: check ref_count instead of lru before migration 096c5b1fde51 mm: add folio_expected_ref_count() for reference count calculation 23da4e0bb2a3 vmxnet3: unregister xdp rxq info in the reset path ca8938704142 KVM: SVM: Set/clear SRSO's BP_SPEC_REDUCE on 0 <=> 1 VM count transitions e5a3331a2e98 x86/bugs: KVM: Add support for SRSO_MSR_FIX f9c6aec2a6dd x86/bugs: Add SRSO_USER_KERNEL_NO support 0a3ac13d8686 platform/x86: asus-wmi: Re-add extra keys to ignore_key_wlan quirk 7228ed156377 platform/x86: asus-wmi: Fix ROG button mapping, tablet mode on ASUS ROG Z13 a89c34babc2e io_uring: fix incorrect io_kiocb reference in io_link_skb 922338efaad6 smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path 24c1106504c6 crypto: af_alg - Set merge to zero early in af_alg_sendmsg 6ae90a2baf92 smb: client: let smbd_destroy() call disable_work_sync(&info->post_send_credits_work) b814660334bb smb: client: fix filename matching of deferred files ea5cbcecd54d drm/xe: Fix a NULL vs IS_ERR() in xe_vm_add_compute_exec_queue() f108c98c7005 drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path 0da73f782769 drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ 503de75db426 drm/xe/tile: Release kobject for the failure path 22814abfd961 ASoC: Intel: catpt: Expose correct bit depth to userspace b51ded0f604e ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message e5c10cec7a1b ASoC: wm8974: Correct PLL rate rounding 987b1d5e39b9 ASoC: wm8940: Correct typo in control name ccba708502b6 ASoC: wm8940: Correct PLL rate rounding 695673eb5711 io_uring/kbuf: drop WARN_ON_ONCE() from incremental length check 93e9d0293d3b io_uring/msg_ring: kill alloc_cache for io_kiocb allocations e6b2b4a0ffd8 io_uring: include dying ring in task_work "should cancel" state d7a38ee4f0be io_uring: backport io_should_terminate_tw() 9b71bfefc405 io_uring/cmd: let cmds to know about dying task 9ffc5f132a35 ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx acab5c56a6fa selftests: mptcp: avoid spurious errors on TCP disconnect 2b5b0674686f selftests: mptcp: connect: catch IO errors on listen side ca261278c6b7 mptcp: propagate shutdown to subflows when possible 60b07b9f6093 rds: ib: Increment i_fastreg_wrs before bailing out 21ba85d9d508 net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer 232e74984061 drm/amd/display: Allow RX6xxx & RX7700 to invoke amdgpu_irq_get/put 2ae6d79a769b KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active bd5524ec7155 mmc: mvsdio: Fix dma_unmap_sg() nents value 6dbac7d814a7 ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S 9c534dbfd172 ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed d1c96316e4c1 ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface bf46ed89bf24 btrfs: tree-checker: fix the incorrect inode ref size check cd92c8ab336c iommu/amd/pgtbl: Fix possible race while increase page table level c023b4f4444f iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() 1e68a5f046e9 LoongArch: Check the return value when creating kobj 05a76baf2700 LoongArch: Align ACPI structures if ARCH_STRICT_ALIGN enabled 382f5ff57010 LoongArch: vDSO: Check kcalloc() result in init_vdso() 040f278cc1a5 LoongArch: Fix unreliable stack for live patching b6f29fa5f603 objtool/LoongArch: Mark special atomic instruction as INSN_BUG type 89d40cc647da objtool/LoongArch: Mark types based on break immediate code 1766f14c8f97 LoongArch: Update help info of ARCH_STRICT_ALIGN cbb8cd66d0bc mm: revert "mm: vmscan.c: fix OOM on swap stress test" f6e161f3fa99 gup: optimize longterm pin_user_pages() for large folio f8f64254bca5 dm-stripe: fix a possible integer overflow cb58eaad2235 dm-raid: don't set io_min and io_opt for raid1 7061e566ce5d power: supply: bq27xxx: restrict no-battery detection to bq27000 f91359651678 power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery 9aee87da5572 crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg 1adc72411f3d nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* 9644798294c7 ksmbd: smbdirect: verify remaining_data_length respects max_fragmented_recv_size 8be498fcbd5b ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer e97c45c770f5 perf/x86/intel: Fix crash in icl_update_topdown_event() ff27e23b311f octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() 6e33a7eed587 cnic: Fix use-after-free bugs in cnic_delete_task acf8d06b8b97 net: liquidio: fix overflow in octeon_init_instr_queue() f07c925bb70e Revert "net/mlx5e: Update and set Xon/Xoff upon port speed set" 208640e6225c tls: make sure to abort the stream if headers are bogus fa4749c06564 tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). 0c691ea3852c octeon_ep: fix VF MAC address lifecycle handling 4c0bfb2dc6ab bonding: don't set oif to bond dev when getting NS target destination d1f3db4e7a3b net/mlx5e: Harden uplink netdev access against device unbind bec504867acc igc: don't fail igc_probe() on LED setup error 610332f7ac20 i40e: remove redundant memory barrier when cleaning Tx descs 80555adb5c89 ice: fix Rx page leak on multi-buffer frames 1644ee7696f3 ice: store max_frame and rx_buf_len only in ice_rx_ring 3e3be7bbe4a5 net: natsemi: fix `rx_dropped` double accounting on `netif_rx()` failure 13e7a6e96076 selftests: mptcp: sockopt: fix error messages 10e54bf7cb6e mptcp: tfo: record 'deny join id0' info bb7a3f09e9d4 selftests: mptcp: userspace pm: validate deny-join-id0 flag 7f5b09cc84e0 mptcp: set remote_deny_join_id0 on SYN recv 9a958802080c bonding: set random address only when slaves already exist 660b2a8f5a30 qed: Don't collect too many protection override GRC elements 5f445eb25990 net/tcp: Fix a NULL pointer dereference when using TCP-AO with TCP_REPAIR 79320035973f dpaa2-switch: fix buffer pool seeding for control traffic 3112c70b2e01 um: Fix FD copy size in os_rcv_fd_msg() 00e98b5a6903 um: virtio_uml: Fix use-after-free after put_device in probe 9c416e76a57f btrfs: fix invalid extref key setup when replaying dentry ded4d207a320 cgroup: split cgroup_destroy_wq into 3 workqueues eed66faed623 pcmcia: omap_cf: Mark driver struct with __refdata to prevent section mismatch 8df33f4d4a0b wifi: mac80211: fix incorrect type for ret 32adb020b0c3 wifi: mac80211: increase scan_ies_len for S1G 814952c1b1ff ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported b146e0434feb nvme: fix PI insert on write 2203ef417044 wifi: wilc1000: avoid buffer overflow in WID string configuration (From OE-Core rev: 28c0056b24be0833bca4c3c86404292d95ad377a) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.16: update CVE exclusions (6.16.9)Bruce Ashfield2025-10-011-5/+53
| | | | | | | | | | | | | | | | | | Data pulled from: https://github.com/CVEProject/cvelistV5 1/1 [ Author: cvelistV5 Github Action Email: github_action@example.com Subject: 1 changes (1 new | 0 updated): - 1 new CVEs: CVE-2025-11135 - 0 updated CVEs: Date: Mon, 29 Sep 2025 01:40:51 +0000 ] (From OE-Core rev: c764baf02d9a0291acb5f4a70a2f86a56dc308be) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/6.16: update to v6.16.9Bruce Ashfield2025-10-013-20/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating linux-yocto/6.16 to the latest korg -stable release that comprises the following commits: b0d8acc71198 Linux 6.16.9 f9fc28d1451b samples/damon/prcl: avoid starting DAMON before initialization 40108f69c372 clk: sunxi-ng: mp: Fix dual-divider clock rate readback f9fa006e3527 samples/damon/mtier: avoid starting DAMON before initialization 8f7dd196be59 samples/damon: change enable parameters to enabled 1338fb5d576a samples/damon/prcl: fix boot time enable crash 941452199941 dt-bindings: serial: 8250: move a constraint 95c9489abfc4 dt-bindings: serial: 8250: spacemit: set clocks property as required ceee5585720a dt-bindings: serial: 8250: allow clock 'uartclk' and 'reg' for nxp,lpc1850-uart fb0b1ef7055b mptcp: pm: nl: announce deny-join-id0 flag 46d6ff0da889 platform/x86: asus-wmi: Re-add extra keys to ignore_key_wlan quirk 1aa91f3d4f16 platform/x86: asus-wmi: Fix ROG button mapping, tablet mode on ASUS ROG Z13 50a98ce1ea69 io_uring: fix incorrect io_kiocb reference in io_link_skb 0991418bf98f smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path 9617c3ede9ff smb: client: fix file open check in __cifs_unlink() 5ba113d0b049 io_uring/msg_ring: kill alloc_cache for io_kiocb allocations 045ee26aa392 crypto: af_alg - Set merge to zero early in af_alg_sendmsg 3fabb1236f2e smb: client: let smbd_destroy() call disable_work_sync(&info->post_send_credits_work) ac6fbc3d0030 smb: client: use disable[_delayed]_work_sync in smbdirect.c a39e32f03183 smb: client: fix filename matching of deferred files 581fb78e0388 smb: client: let recv_done verify data_offset, data_length and remaining_data_length cbda551b90a7 smb: client: make use of struct smbdirect_recv_io 089ea68aae42 smb: smbdirect: introduce struct smbdirect_recv_io 86b4bddb8292 smb: client: make use of smbdirect_socket->recv_io.expected f2ffba55b686 smb: smbdirect: introduce smbdirect_socket.recv_io.expected dd1a415dcfd5 drm/xe/guc: Set RCS/CCS yield policy 97207a4fed53 drm/xe/guc: Enable extended CAT error reporting 56f34936bf8c drm/xe: Fix error handling if PXP fails to start 09b473a80c1c ALSA: usb: qcom: Fix false-positive address space check b45cabfa717d drm/xe: Fix a NULL vs IS_ERR() in xe_vm_add_compute_exec_queue() e3fe0101463a drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path 1a7ea294d57f drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ e6a1df8cf275 drm/xe/pf: Drop rounddown_pow_of_two fair LMEM limitation f32a0226e848 drm/xe/tile: Release kobject for the failure path 65c5cfbd6d93 ASoC: amd: acp: Fix incorrect retrival of acp_chip_info f7229775e41d iommu/amd: Fix alias device DTE setting 34f3a9e04e73 ASoC: Intel: catpt: Expose correct bit depth to userspace f6433733326b ASoC: SDCA: Fix return value in sdca_regmap_mbq_size() 9ff967d7e8d9 ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message cd59ca8f75db ASoC: codec: sma1307: Fix memory corruption in sma1307_setting_loaded() 7c28b31b2209 ASoC: wm8974: Correct PLL rate rounding badf6143198e ASoC: wm8940: Correct typo in control name 7a372ac1e890 ASoC: wm8940: Correct PLL rate rounding 519b95c74f40 ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx ee8d393af37e selftests: mptcp: avoid spurious errors on TCP disconnect 47f8d4403995 selftests: mptcp: connect: catch IO errors on listen side 80d38ea27a1e mptcp: propagate shutdown to subflows when possible c62000bf27db rds: ib: Increment i_fastreg_wrs before bailing out bc509293c9d4 crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() 27d94a2a52cb gpiolib: acpi: initialize acpi_gpio_info struct 21a39b958b4b net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer 6db60106a07f io_uring: include dying ring in task_work "should cancel" state f757ab3db457 io_uring/io-wq: fix `max_workers` breakage and `nr_workers` underflow 898aaf78480b drm/amd: Only restore cached manual clock settings in restore if OD enabled 20f87640ebe7 drm/amd/display: Allow RX6xxx & RX7700 to invoke amdgpu_irq_get/put 1ff89f5627ef drm/amdgpu: suspend KFD and KGD user queues for S0ix b477c5668ec6 drm/amdkfd: add proper handling for S0ix 0e2db61cc589 KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active c0603b80436d x86/sev: Guard sev_evict_cache() with CONFIG_AMD_MEM_ENCRYPT 79a9ba8da904 mmc: sdhci-uhs2: Fix calling incorrect sdhci_set_clock() function 7650c994ced2 mmc: sdhci-pci-gli: GL9767: Fix initializing the UHS-II interface during a power-on 7186d8e8bd96 mmc: sdhci: Move the code related to setting the clock from sdhci_set_ios_common() into sdhci_set_ios() d0b7ff384b7a mmc: mvsdio: Fix dma_unmap_sg() nents value 66e6d1c92806 ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S cc336b242ea7 ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed 59c4accddfeb ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface 8276c97dccee ASoC: SDCA: Add quirk for incorrect function types for 3 systems 417ed00d48e7 btrfs: tree-checker: fix the incorrect inode ref size check 359613f2fa00 iommu/s390: Make attach succeed when the device was surprise removed 17a58caf3863 iommu/s390: Fix memory corruption when using identity domain 7d462bdecb7d iommu/amd/pgtbl: Fix possible race while increase page table level b0c0e231060a iommu/amd: Fix ivrs_base memleak in early_amd_iommu_init() 7ff7d16649b2 iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() 1c731284374a LoongArch: KVM: Fix VM migration failure with PTW enabled 960eedb14caf LoongArch: KVM: Avoid copy_*_user() with lock hold in kvm_pch_pic_regs_access() 55ba91b4e04d LoongArch: KVM: Avoid copy_*_user() with lock hold in kvm_eiointc_sw_status_access() 105605ca76e9 LoongArch: KVM: Avoid copy_*_user() with lock hold in kvm_eiointc_regs_access() 291d4b01d3b1 LoongArch: KVM: Avoid copy_*_user() with lock hold in kvm_eiointc_ctrl_access() 401363c839cb LoongArch: Handle jump tables options for RUST 1967642780cf LoongArch: Make LTO case independent in Makefile db65fea5f0aa LoongArch: Check the return value when creating kobj 5f2b63a398ed LoongArch: Align ACPI structures if ARCH_STRICT_ALIGN enabled a417571950f9 LoongArch: vDSO: Check kcalloc() result in init_vdso() 2feeecd7c685 LoongArch: Fix unreliable stack for live patching 5dbbc7b04c14 objtool/LoongArch: Mark special atomic instruction as INSN_BUG type e0aefa8f4612 objtool/LoongArch: Mark types based on break immediate code 953138ff0ff6 LoongArch: Update help info of ARCH_STRICT_ALIGN 1eda9ab8da6b mm: folio_may_be_lru_cached() unless folio_test_large() fb4e6d587a27 mm: revert "mm: vmscan.c: fix OOM on swap stress test" d0c8ba94cb70 mm/gup: local lru_add_drain() to avoid lru_add_drain_all() 163843e8c8f3 gup: optimize longterm pin_user_pages() for large folio 3958f9ec7251 mm: revert "mm/gup: clear the LRU flag of a page before adding to LRU batch" fdac0a3f58c0 mm/gup: check ref_count instead of lru before migration ee27658c239b dm-stripe: fix a possible integer overflow ba3a78db47ec dm-raid: don't set io_min and io_opt for raid1 e8f496001e0c btrfs: initialize inode::file_extent_tree after i_mode has been set 8ae09726773a Revert "sched_ext: Skip per-CPU tasks in scx_bpf_reenqueue_local()" a4ee54e68282 power: supply: bq27xxx: restrict no-battery detection to bq27000 d18d7035ecb8 power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery 45bcf60fe49b crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg 7b7361da9e7f nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* ff750e9f2c4d zram: fix slot write race condition c64b915bb3d9 ksmbd: smbdirect: verify remaining_data_length respects max_fragmented_recv_size 529b121b00a6 ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer 5ca20bb7b4bd octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() 0627e1481676 cnic: Fix use-after-free bugs in cnic_delete_task 45f71f4ac4aa net: liquidio: fix overflow in octeon_init_instr_queue() 6e1675c8b612 net: clear sk->sk_ino in sk_set_socket(sk, NULL) 53222fc8ebbc Revert "net/mlx5e: Update and set Xon/Xoff upon port speed set" 61ca2da5fb8f tls: make sure to abort the stream if headers are bogus ae313d14b45e tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). 0357a37b4a8b octeon_ep: fix VF MAC address lifecycle handling e2019c7d3a3e bonding: don't set oif to bond dev when getting NS target destination 948381b58298 net/mlx5e: Add a miss level for ipsec crypto offload 8df354eb2dd6 net/mlx5e: Harden uplink netdev access against device unbind 805c7df4faca doc/netlink: Fix typos in operation attributes f05e82d85532 igc: don't fail igc_probe() on LED setup error 3ce36b3b9c69 ixgbe: destroy aci.lock later within ixgbe_remove path a4a4b796dcf6 ixgbe: initialize aci.lock before it's used 5ac700c61648 i40e: remove redundant memory barrier when cleaning Tx descs fcb5718ebfe7 ice: fix Rx page leak on multi-buffer frames 4f21a0b3c8c2 net: natsemi: fix `rx_dropped` double accounting on `netif_rx()` failure 5735f1fb81a8 selftests: mptcp: sockopt: fix error messages 7f501faddb3c mptcp: tfo: record 'deny join id0' info fa9a7f272b01 selftests: mptcp: userspace pm: validate deny-join-id0 flag f679e3dc6c01 mptcp: set remote_deny_join_id0 on SYN recv f3439ed58636 bonding: set random address only when slaves already exist 8b1dc0217f96 net: dst_metadata: fix IP_DF bit not extracted from tunnel headers 70affe82e38f qed: Don't collect too many protection override GRC elements 1c24b132c119 octeon_ep: Validate the VF ID 71571e187106 rxrpc: Fix untrusted unsigned subtract 8ac99c57029e rxrpc: Fix unhandled errors in rxgk_verify_packet_integrity() 64e76fcb5311 dpll: fix clock quality level reporting 993b734d31ab net/tcp: Fix a NULL pointer dereference when using TCP-AO with TCP_REPAIR d0c3f85a041a dpaa2-switch: fix buffer pool seeding for control traffic e1fa8f786c8d net/mlx5: Not returning mlx5_link_info table when speed is unknown 4c2c59cc838c um: Fix FD copy size in os_rcv_fd_msg() c2ff91255e01 um: virtio_uml: Fix use-after-free after put_device in probe 856e039ded02 smb: server: let smb_direct_writev() respect SMB_DIRECT_MAX_SEND_SGES 09ea55d02c89 pcmcia: omap_cf: Mark driver struct with __refdata to prevent section mismatch 0835c4592344 wifi: mac80211: fix incorrect type for ret 0dbad5f5549e wifi: mac80211: increase scan_ies_len for S1G 745418fc8229 wifi: mt76: do not add non-sta wcid entries to the poll list 778a062c131e ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported 0cdf320eb46c nvme: fix PI insert on write ae50f8562306 wifi: wilc1000: avoid buffer overflow in WID string configuration d06a83038bd6 perf maps: Ensure kmap is set up for all inserts 314a92e5950f btrfs: zoned: fix incorrect ASSERT in btrfs_zoned_reserve_data_reloc_bg() eff2bb3b300b btrfs: fix invalid extref key setup when replaying dentry 05e0b03447cf cgroup: split cgroup_destroy_wq into 3 workqueues (From OE-Core rev: 82225c9148038b66ca3ff408f880f83eb7c45a57) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-setup-build: fix dash supportYoann Congal2025-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | Being minimalist, dash does not support the (non-POSIX) feature of passing an argument while sourcing a script. Like in . <some path>/oe-init-build-env <build dir> With dash, one must instead use: cd <some path> set <build dir> # puts <build dir> in $1 . ./oe-init-build-env # can only be called from its directory in dash oe-setup-build generate a sourcable "init-build-env" script, this script must use the above snippet to be used in dash. (From OE-Core rev: 35c90011824845b40066b7747b256f1cd31b0dba) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* expat: upgrade to 2.7.3Ross Burton2025-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Security fixes: - Fix alignment of internal allocations for some non-amd64 architectures (e.g. sparc32); fixes up on the fix to CVE-2025-59375 from #1034 (of Expat 2.7.2 and related backports) - Fix a class of false positives where input should have been rejected with error XML_ERROR_ASYNC_ENTITY; regression from CVE-2024-8176 fix pull request #973 (of Expat 2.7.0 and related backports). Please check the added unit tests for example documents. Other changes: - Prove and regression-proof absence of integer overflow from function expat_realloc - Remove "harmless" cast that truncated a size_t to unsigned - Autotools: Remove "ln -s" discovery - docs: Be consistent with use of floating point around XML_SetAllocTrackerMaximumAmplification - docs: Make it explicit that XML_GetCurrentColumnNumber starts at 0 - docs: Better integrate the effect of the activation thresholds - docs: Fix an in-comment typo in expat.h - docs: Fix a typo in README.md - docs: Improve change log of release 2.7.2 - xmlwf: Resolve use of functions XML_GetErrorLineNumber and XML_GetErrorColumnNumber - Windows: Normalize .bat files to CRLF line endings - Version info bumped from 12:0:11 (libexpat*.so.1.11.0) to 12:1:11 (libexpat*.so.1.11.1); see https://verbump.de/ for what these numbers do (From OE-Core rev: 6b1833cd2eb78be55ba03da73937358fcf25d9ec) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/cmake: unset LDFLAGS in toolchain-native.bbclassRoss Burton2025-10-011-0/+9
| | | | | | | | | | | | | | | | | | | | | | If a recipe is using toolchain-native.cmake to build native portion in a non-native build, the target LDFLAGS from the environment will leak into the native build. This was noticed as building a SDK with clang means that LDFLAGS contains a --dynamic-loader argument, so native binaries were trying to use the target loader. There are several variables that are set from LDFLAGS[1] so instead of setting them all, we can simply unset the environment variable in the toolchain. [1] https://cmake.org/cmake/help/latest/envvar/LDFLAGS.html (From OE-Core rev: f9fa240a6788188174c8080a78018ed9ce402f54) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/bblayers.py: add tests for adding new built-in fragmentsAntonin Godard2025-10-012-0/+31
| | | | | | | | | | | | | | | | | | | | | Add discussed in [1], our best option for customizing built-in fragments is to pass them from a layer configuration. In short, the reason is that our statement must be parsed before the addfragments call is parsed.We also have to use the :append override as using += would override the original definition of OE_FRAGMENTS_BUILTIN (since it uses a ?= assignment). Provide a test case for customizing built-in fragments with meta-selftest. [1]: https://lore.kernel.org/yocto-docs/20250925-fragments-v1-0-c9f747361fb2@bootlin.com/T/#m9f7c9f110c084eba17e0f64d8b2ac7a88af3f38e Cc: Alexander Kanavin <alex.kanavin@gmail.com> (From OE-Core rev: 38cbf4c0ce5173dc3080fa0fbb3ec3e7926c8137) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tiff: ignore CVE-2025-8851Peter Marko2025-10-011-0/+1
| | | | | | | | | | | This is fixed in v4.7.0, however cve_check cannot match it as NVD says "Up to (excluding) 2024-08-11". (From OE-Core rev: 66349865ac048ae8e5a81b29c50c68503053f74e) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tiff: upgrade 4.7.0 -> 4.7.1Peter Marko2025-10-019-380/+3
| | | | | | | | | | | | | | Removed patches included in this new release License-Update: BSD license added based on [1] [1] https://gitlab.com/libtiff/libtiff/-/commit/a0b623c7809ea2aa4978d5d7b7bd10e519294c78 (From OE-Core rev: 9161c31aa37341f758fd8f3d095177e8b6de1448) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchtest: Use raw strings for regex patternsPaul Barker2025-10-012-12/+12
| | | | | | | | | | | | This fixes several 'SyntaxWarning: invalid escape sequence' messages printed when running patchtest. Cc: Trevor Gamblin <tgamblin@baylibre.com> (From OE-Core rev: c585977a6b55db93b7f432280ae4251aa9bc6b6c) Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers/create: Improve help message for layerid argumentPaul Barker2025-10-011-1/+1
| | | | | | | | | | | | | | | 'Layer ID' isn't a commonly used term in our help messages or documentation, so clarify that this is the identifier used for the new layer in BBFILE_COLLECTIONS. Also clarify that the default is the basename of the layerdir argument if a layer ID is not separately provided. (From OE-Core rev: bb8bd71b1aba31aeb0c1d2fbcae36da26865dc57) Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unzip: remove invalid UPSTREAM_CHECK_REGEXChangqing Li2025-10-011-3/+0
| | | | | | | | | | | After SRC_URI is changed to sourceforge, this UPSTREAM_CHECK_REGEX become invalid, just remove it. (From OE-Core rev: b5aec20d6139fb45501b383cd5cc2ef944cc6dd4) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vim: upgrade 9.1.1652 -> 9.1.1683Divya Chellam2025-10-011-2/+2
| | | | | | | | | | | | | | Handles CVE-2025-9389 Changes between 9.1.1652 -> 9.1.1683 ==================================== https://github.com/vim/vim/compare/v9.1.1652...v9.1.1683 (From OE-Core rev: ad24eedbbef303e67acb1241ed54c253ec5ab50c) Signed-off-by: Divya Chellam <divya.chellam@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* baremetal-helloworld: set UPSTREAM_CHECK_COMMITSChangqing Li2025-10-011-1/+1
| | | | | | | | | | | | | | set UPSTREAM_CHECK_COMMITS to make new commit is reported Test result(change SRCREV to an old one): $devtool check-upgrade-status baremetal-helloworld baremetal-helloworld 0.1 new commits Alejandro Hernandez <alejandro@enedino.org> db2bf750eaef7fc0832e13ada8291343bbcc3afe (From OE-Core rev: 3d7d324ca0ea242f1455332a20ac7b0f3cdcd761) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cwautomacros: delete the recipeAlexander Kanavin2025-10-012-26/+0
| | | | | | | | | | | This is a long-obsolete set of custom autotools macros; 'which' was the last consumer in core or meta-oe. (From OE-Core rev: 6d1470f6d244c08e3473073d0c2d57a97d2eeb17) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* which: update 2.21 -> 2.23, build with mesonAlexander Kanavin2025-10-014-38/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This (and 2.22) is a first release in many years. Rather than try to use upstream's absurdly overblown, incompatible build system (see below), I added a small-ish meson file. This means: - drop tweaks and dependency on cwautomacros as that is no longer used - drop patch as configure.ac has been rewritten, and the recipe is using meson anyway - drop --disable-iberty for the same reason In this realease, cwautomacros has been replaced by an equally custom, weird set of macros, written by 'which' maintainer: https://github.com/CarloWood/cwm4 - one effect of that is that autoreconf isn't happy with which's configure.ac and won't run; one is supposed to use a custom script instead: https://github.com/CarloWood/cwm4/blob/master/scripts/bootstrap.sh - alas, that script is not shipped in tarballs; the maintainer wants everyone to trust their 200k configure script (hello xz backdoor) - building from git (where the script exists) is not impossible, but that has no version tags All this 'special handling' for what, exactly? Five .c files to produce one single-function executable, and one manpage. Wich should all be in coreutils to begin with. GNU's attachment to autotools defies reason. (From OE-Core rev: 600545a0ef313e7df5a0f25eba17b73b0f410489) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* test-manual/yocto-project-compatible.rst: fix a typoAntonin Godard2025-09-261-1/+1
| | | | | | | | | | Fix a typo in yocto-project-compatible.rst. Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de> (From yocto-docs rev: a84c234acfedfa714419006c743405e2f9acaedc) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guides/release-notes-5.3: using runqemu with compressed imagesYoann Congal2025-09-261-0/+7
| | | | | | | | | | | | | | | In OE-core commits: * b5f8c3e029 (selftest: runqemu: add tests for booting zst compressed image, 2025-07-31) * e069fe2480 (runqemu: Add support for running compressed .zst rootfs images, 2025-07-31) runqemu gained the ability to run compressed image (+associated test). Add this information to the release-notes for 5.3. (From yocto-docs rev: f268c1b649227d533d02e1a6df797b784fcf80de) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: make "Crediting contributors" part of ↵Quentin Schulz2025-09-261-25/+29
| | | | | | | | | | | | | | | | | | | | | "Commit your changes" There's no need to differentiate crediting contributors from committing your changes, so let's simply make it the last step of "Commit your changes" section. This simply indents the text so it's now part of "Commit your changes" list instead of the main list in the "Implement and commit changes" section. Because of this reorganisation, the instruction to use "git commit --amend" to add the contributors is moved to a note, and the first few sentences are reworded to better match the wording of other items in the "Commit your changes" list of instructions. (From yocto-docs rev: eff4d14e28d323ebfdaeb0c5c805b5f1e2ad153d) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: number instruction list in commit your ↵Quentin Schulz2025-09-261-76/+76
| | | | | | | | | | | | | changes ... so that it's clear that you need to read and follow each and every instruction in this list. (From yocto-docs rev: c628a489f081925fabaabb5acac6752251150269) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: reword commit message instructionsQuentin Schulz2025-09-261-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | This should hopefully make it clearer what is expected from the contributor. This follows my understanding of git-commit(1)[1] where the following is a git commit message: """ git commit title git commit description """ I'm putting the "Fixes [YOCTO" line in "body of the commit message" so it's understood as being different from the git commit description so that the note admonition allowing us to have an empty commit description doesn't apply to the "Fixes [YOCTO" line. [1] https://www.man7.org/linux/man-pages/man1/git-commit.1.html#DISCUSSION (From yocto-docs rev: b84903a760350bd118c56ea9ce4e98039edf6e55) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: make the Cc tag follow kernel guidelinesQuentin Schulz2025-09-261-1/+1
| | | | | | | | | | | | | The kernel docs specifies[1] a Cc: tag and not CC: tag, so let's align with that. [1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by (From yocto-docs rev: f800fef4e9e2c1d3584ac49be8324638d2923b17) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: align CC tag descriptionQuentin Schulz2025-09-261-1/+1
| | | | | | | | | | | | The other tag descriptions have the double colon outside of the highlight, and start the sentence with a lowercase word, so let's align the CC tag with those. (From yocto-docs rev: f116e93fb335e9d0f85891c4cb501bcf55b18ccf) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: clarify example with Yocto bug IDQuentin Schulz2025-09-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The example could be understood as the content of the commit message once the editor (git config core.editor) opens, where the first line is the actual commit title and not the commit description. This example would make the Fixes line the commit title, which is not what we want. In short, according to my understanding of git-commit(1): The following is a git commit message: """ git commit title git commit description """ Reported-by: Barne Carstensen <barne.carstensen@danfoss.com> (From yocto-docs rev: a5862406bf3230befe9db9f2539bbbc86c02015d) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>