linux/poky.git, branch scarthgap

pseudo: Upgrade 1.9.6 -> 1.9.7

2026-06-10T13:35:21+00:00

Pulls in fixes to rename/renameat/renameat2: Changqing Li (1): renameat2/renameat: only ignore when both old and new path are not in PSEUDO_INCLUDE_PATHS Mark Hatle (4): run_tests.sh: Allow the user to specify specific tests to run tests: Add mv then hardlink testing rename: only ignore when both old and new path are not in PSEUDO_INCLUDE_PATHS Makefile.in: Bump version to 1.9.7 (From OE-Core rev: e2864ea1ac022e43af92badc701fa1e2a9571f46) Signed-off-by: Richard Purdie (cherry picked from commit 17567738711d525d9f2b85e54ace2048901e4c34) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

pseudo: Update 1.9.5 -> 1.9.6

2026-06-10T13:35:21+00:00

Pulls in the changes: * Makefile.in: Bump version to 1.9.6 * pseudo_util.c: Fix symlink processing for symlinkat and related * test: Add test symlinkat and related * ports/unix: realpath: Fix chroot processing * test: Add test cases for canonicalize functions * ports/unix: fts_open: Fix chroot behavior * ports/unix: fts_*: Certain functions were incorrectly returning stat data * test: Add fts test case * test: Add test for linkat chroot path stripping * linkat: Avoid a segmentation fault * Only copy xattrs on a rename if it's cross-filesystem (From OE-Core rev: 1414f3513099a9a956ec4f602354aa00008e2aff) Signed-off-by: Richard Purdie (cherry picked from commit 50e769a598e79ed4600f7362d5f40799a48f9273) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

pseudo: Upgrade to 1.9.5

2026-06-10T13:35:21+00:00

This adds a wrapper for the __open_2 function This was breaking shadow and the real reason for the open() call changes. Add the missing wrapper to properly fix this. (From OE-Core rev: 876e6497f3323d74d9ac8ce303ed5165a7fda283) Signed-off-by: Richard Purdie (cherry picked from commit 8ea63d320aba32d3894cace9e71e850bdff1d6b2) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

pseudo: Upgrade to 1.9.4

2026-06-10T13:35:21+00:00

Update to pull in a full openat2 wrapper which works on Fedora 44. This update includes the commits: * Makefile.in: Bump version to 1.9.4 * test: Add renameat2 test cases * test: Add openat2 test cases * makewrappers/openat2: Add preserve_path option * openat2: Implement openat2 wrapper * ports/linux/guts/renameat2.c: Add comment why this isn't implemented * Add b4 configuration * pseudo_setupenvp: Handle malloc failure safely * pseudo_setupenvp: Allocate space for new env vars if needed (From OE-Core rev: 9075b66e1f9161407056924954b3d5507f6d8384) Signed-off-by: Richard Purdie (cherry picked from commit b2bd1d114fafe1e797149e02e4c08194d529cfde) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

tzdata/tzcode-native: upgrade 2026a -> 2026b

2026-06-10T13:35:21+00:00

The 2026b release contains the following changes: Briefly: British Columbia moved to permanent -07 on 2026-03-09. Some more overflow bugs have been fixed in zic. Changes to future timestamps British Columbia’s 2026-03-08 spring forward was its last foreseeable clock change, as it moved to permanent -07 thereafter. (Thanks to Arthur David Olson.) Although the change to permanent -07 legally took place on 2026-03-09, temporarily model the change to occur on 2026-11-01 at 02:00 instead. This works around a limitation in CLDR v48.2 (2026-03-17). This temporary hack is planned to be removed after CLDR is fixed. Changes to code zic no longer mishandles a last transition to a new time type. zic no longer overflows a buffer when generating a TZ string like "PST-167:59:58PDT-167:59:59,M11.5.6/-167:59:59,M12.5.6/-167:59:59", which can occur with adversarial input. (Thanks to Naveed Khan.) zic no longer generates a longer TZif file than necessary when an earlier time zone abbreviation is a suffix of a later one. As a nice side effect, zic no longer overflows a buffer when given a long series of abbreviations, each a suffix of the next. (Buffer overflow reported by Arthur Chan.) zic no longer overflows an int when processing input like ‘Zone Ouch 2147483648:00:00 - LMT’. The int overflow can lead to buffer overflow in adversarial cases. (Thanks to Naveed Khan.) zic now checks for signals more often. (From OE-Core rev: 37dab321242e06d2940c4221e4a13e68265d696f) Signed-off-by: Ankur Tyagi Signed-off-by: Mathieu Dubois-Briand (cherry picked from commit dda7d55396e0c5258cba58af7e990ab3813bf108) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

linux-yocto/6.6: update CVE exclusions (6.6.127)

2026-06-10T13:35:21+00:00

Regenerated to fix this warning: WARNING: linux-yocto-6.6.127+git-r0 do_cve_check: Kernel CVE status needs updating: generated for 6.6.123 but kernel is 6.6.127 $ ./meta/recipes-kernel/linux/generate-cve-exclusions.py .../cvelistV5/ 6.6.127 > meta/recipes-kernel/linux/cve-exclusion_6.6.inc Generated at 2026-05-27 12:02:49.732909+00:00 for kernel version 6.6.127 From cvelistV5 cve_2026-05-27_0900Z (From OE-Core rev: d0d02d0f45b4c5108ae648fb16d2a2a0dc1ae0e7) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

wic: filemap: use separate fd for SEEK_HOLE probes

2026-06-10T13:35:20+00:00

While working on splitting-out wic from oe-core, on my openSUSE Leap 16.0 machine, the moment I split wic out, 2 oe-selftests always failed with 100% reproducibility: - wic.ModifyTests.test_wic_cp_ext - wic.Wic2.test_expand_mbr_image In both cases the symptom is the same: the filesystem has inode tables that are completely zeroed out. Both issues are linked together to the same underlying fault. FilemapSeek._get_ranges() is a generator. Due to the nature of finding each hole/data extent one at a time using the lseek() system call, it calls os.lseek() on a raw file descriptor, then yields, then the caller, sparse_copy(), calls file.seek() + file.read() on a Python BufferedReader wrapping that same fd — then the generator resumes and calls os.lseek() again. This interleaving of raw os.lseek() and buffered I/O on the same fd is undefined behaviour from Python's perspective. The BufferedReader tracks its own idea of the fd's position and buffer contents; os.lseek() changes the position behind its back. This can corrupt its internal state and cause read() to return stale/zero data. This code, however, has existed in wic since it was written, so why was it not noticed before? It turns out this bug was being masked by a number of implementation details that changed, especially when wic was split out for oe-core. These changes conspired together to cause the bug to be triggered. One of the root causes of this bug is that Python 3.14 increased the default buffer size from 8KB to 128KB[1]. With 8 KB buffers, read()s either go through the direct-read path leaving the buffer empty, or if it fills in 8KB chunks the buffer is fully drained. Either way, with a small buffer, read()s do a real raw seek. No fast path. No corruption. With a 128KB buffer, however, a much larger window exists where BufferedReader.seek() can take the fast-path after the raw file descriptor has already been repositioned by os.lseek() in the generator. With the smaller buffer, this window was too narrow to hit in practice. This is fixed by opening a second file object in FilemapSeek.__init__() dedicated to SEEK_DATA/SEEK_HOLE probes, leaving the data-reading handle (self._f_image) untouched. This explains why the corruption is deterministic and tied to specific block boundaries, why it only manifests with the split-out version using Python 3.14 (on systems that are using Python versions less than 3.14 on the host), and why using a separate file descriptor for reading bypasses the issue entirely. This is not an intermittent bug. For a more detailed explanation including log files, in-depth analysis, and a standalone Python reproducer, please see the linked bugzilla entry. Fixes: [YOCTO #16197] [1] https://github.com/python/cpython/commit/b1b4f9625c5f2a6b2c32bc5ee91c9fef3894b5e6 b1b4f9625c5f ("gh-117151: IO performance improvement, increase io.DEFAULT_BUFFER_SIZE to 128k (GH-118144)") AI-Generated: codex/claude-opus-4.6 (xhigh) (From OE-Core rev: 37a45219dd204b07bad40576fefccb2cf85b255c) Signed-off-by: Trevor Woerner Signed-off-by: Richard Purdie (cherry picked from commit 481969844385f2fa40a1230ca50253ec4ff516cd) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

classes/base: prefer gnu-prefixed HOSTTOOLS

2026-06-10T13:35:20+00:00

Ubuntu 25.10 has changed the default coreutils implementation from GNU coreutils to uutils/coreutils. Unfortunately this causes build problems: couldn't allocate absolute path for 'null'. tail: cannot open 'standard input' for reading: No such file or directory install: failed to chown '...': Invalid argument (os error 22) Clear build failures happen in 'install' and 'tail', but there may be further breakage. Luckily, Ubuntu also installs GNU coreutils with a binary prefix of 'gnu', so whilst these issues are root-caused and fixed in either pseudo or uutils we can prefer the gnu-prefixed binaries where they are present. [ YOCTO #16028 ] (From OE-Core rev: b797cc729f6e6951baa988e1c04bac9fb8183a1c) Signed-off-by: Ross Burton Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit 16f2684ebeffa72b5d90525cf9102751b68c298e) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

scripts/install-buildtools: Update to 5.0.18

2026-06-10T13:35:20+00:00

Update to the 5.0.18 release of the 5.0 series for buildtools (From OE-Core rev: 7b2955ae65d4060aaa8f3eda9f3583750606a646) Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

libarchive: Fix CVE-2026-4424

2026-06-10T13:35:20+00:00

Pick patches from [1] and [2] as mentioned in Debian report in [3]. [1] https://github.com/libarchive/libarchive/commit/d379dc0b2976b7207d1ad78f5ed3eb99a5b6d375 [2] https://github.com/libarchive/libarchive/commit/e1907c5832b6489c7b4198b0825f857c93a03c10 [3] https://security-tracker.debian.org/tracker/CVE-2026-4424 (From OE-Core rev: 7fa280872275e194152cc2d355ad39c81a477d50) Signed-off-by: Hugo SIMELIERE (Schneider Electric) Reviewed-by: Bruno VERNAY Signed-off-by: Yoann Congal Signed-off-by: Paul Barker