linux/poky.git/meta/recipes-core/util-linux, branch 5.2_M3

util-linux/util-linux-libuuid: upgrade from 2.40.2 to 2.40.4

2025-02-18T11:56:04+00:00

The following patch dropped because it is in the new version: - 0001-autotools-fix-securedir-and-pam_lastlog2-install.patch libfdisk-cfdisk-and-sfdisk-sector-size-improvements.patch is replaced by two new patches: - 0001-cfdisk-add-sector-size-commanand-line-option.patch - 0002-sfdisk-add-sector-size-commanand-line-option.patch This is because the original patch is a squash of four patches and two of them are in the new version. So extract the remaining two that are not in the current version and make them separate patches for better tracking. (From OE-Core rev: e87b9bccc52bfba0c48db4920c0996d7dd6a0866) Signed-off-by: Chen Qi Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

util-linux-libuuid: use util-linux's CVE_PRODUCT value

2025-02-01T13:20:45+00:00

util-linux and util-linux-libuuid should use the same CVE_PRODUCT since they're the same product. They're just split off for package dependency reasons. Prior to this patch the libuuid recipe gave the wrong CVE_PRODUCT value, causing some CVE check tools to fail on it. (From OE-Core rev: 5c6abb099d579b9451fc2cb38c5d8860cfa6d52f) Signed-off-by: Daniel McGregor Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

util-linux: Document more specific BSD-4-Clause-UC

2025-01-27T15:47:09+00:00

LIC_FILES_CHKSUM in the util-linux recipe already contains the more specific license reference BSD-4-Clause-UC that takes a copyright addendum by University of California into account. License-Update: reference can be more specific (From OE-Core rev: 7cc73cb77e6e783a903978221cb502bb359412f6) Signed-off-by: Bastian Germann Signed-off-by: Richard Purdie

util-linux: Improve PACKAGES_DYNAMIC handling for util-linux-native

2025-01-10T11:23:45+00:00

DEBUG: Assuming util-linux-swapon-native is a dynamic package, but it may not exist DEBUG: Assuming util-linux-swapon-native is a dynamic package, but it may not exist DEBUG: providers for util-linux-swapon-native are: ['util-linux', 'util-linux-native'] DEBUG: sorted runtime providers for util-linux-swapon-native are: ['recipes-core/util-linux/util-linux_2.40.2.bb', 'virtual:native:recipes-core/util-linux/util-linux_2.40.2.bb'] NOTE: Multiple providers are available for runtime util-linux-swapon-native (util-linux, util-linux-native) The PACKAGES_DYANMIC line could match native and non-native packages so tweak to improve -native handling and avoid the above warnings in world builds. (From OE-Core rev: 5577bb4772a76b3e419cf1f8f2a439bc1b15a9b5) Signed-off-by: Richard Purdie

util-linux: add volatile file for lastlog2

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

Add volatile file for lastlog2 to fix runtime error with sysvinit: $ lastlog2 lastlog2: Couldn't read entries for all users lastlog2: Cannot open database (/var/lib/lastlog/lastlog2.db): unable to open database file (From OE-Core rev: 440f4830d1f1bac9d55584fc4e48627920493cb9) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

util-linux: replace local patch with upstream patch

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

There is a better solution upstream to fix the pam_lastlog2 installation issue[1]. Backport this patch to replace the local patch. [1] https://github.com/util-linux/util-linux/pull/3173 (From OE-Core rev: 1c984d0a06cdcba49f8b0acd12edebfeaedf3aa5) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

util-linux: sfdisk sector size improvements

2024-10-22T11:28:18+00:00

Refer to https://github.com/util-linux/util-linux/pull/3237. (From OE-Core rev: 7e37e0addeae3ade4d1634697cde5c8cc619c46a) Signed-off-by: Vince Chang Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

util-linux: Add `findmnt` to the bash completion RDEPENDS

2024-10-18T14:01:04+00:00

The bash completion scripts for `umount`, `fstrim` and `fsfreeze` make use of `findmnt` so add it to the bash completion RDEPENDS. (From OE-Core rev: f8703b486a6ccf39225815362acadafb890ca56e) Signed-off-by: Alban Bedel Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

util-linux/util-linux-libuuid: upgrade from 2.40.1 to 2.40.2

2024-08-23T08:12:38+00:00

Upgrade util-linux from 2.40.1 to 2.40.2. 0001-Revert-autotools-make-pam-install-path-configurable.patch is added to solve a problem of lastlog2 pam module not installed in the expected location. (From OE-Core rev: 2303f28de507ceb88a012647f70b74e0fad6ec4b) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

util-linux: Add PACKAGECONFIG option to mitigate rootfs remount error

2024-08-23T08:12:37+00:00

The 2.39 version of util-linux took new file descriptors based mount kernel API into use. In relation to this change, the upstream release notes in https://github.com/util-linux/util-linux/blob/v2.39/Documentation/releases/v2.39-ReleaseNotes#L14-L21 mention that This change is very aggressive to libmount code, but hopefully, it does not introduce regressions in traditional mount(8) behavior. After observing following failure when booting a board using a bit older 6.1 series kernel together with initramfs rootfs based boot flow [FAILED] Failed to start Remount Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. closer inspection revealed: demoboard ~ # systemctl status -l systemd-remount-fs.service x systemd-remount-fs.service - Remount Root and Kernel File Systems Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; preset: disabled) Active: failed (Result: exit-code) since Wed 2024-08-14 14:53:48 UTC; 1min 22s ago Docs: man:systemd-remount-fs.service(8) https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Process: 76 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE) Main PID: 76 (code=exited, status=1/FAILURE) Aug 14 14:53:48 demoboard systemd-remount-fs[76]: /usr/bin/mount for / exited with exit status 32. Aug 14 14:53:48 demoboard systemd-remount-fs[81]: mount: /: mount point not mounted or bad option. Aug 14 14:53:48 demoboard systemd-remount-fs[81]: dmesg(1) may have more information after failed mount system call. Aug 14 14:53:48 demoboard systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Aug 14 14:53:48 demoboard systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. Aug 14 14:53:48 demoboard systemd[1]: Failed to start Remount Root and Kernel File Systems. also consequentially, 'systemctl status' reported: State: degraded When issuing 'strace -ff mount -o remount /' the failure occurred at mount_setattr(3, "", AT_EMPTY_PATH, {attr_set=MOUNT_ATTR_RDONLY|MOUNT_ATTR_NOATIME|MOUNT_ATTR_NODIRATIME, attr_clr=MOUNT_ATTR_NOSUID|MOUNT_ATTR_NODEV|MOUNT_ATTR_NOEXEC|MOUNT_ATTR_NOATIME|MOUNT_ATTR_STRICTATIME|MOUNT_ATTR_NOSYMFOLLOW|0x40, propagation=0 /* MS_??? */, userns_fd=0}, 32) = -1 EINVAL (Invalid argument) After further investigation, The issue was pinpointed to lack of Linux kernel commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95de4ad173ca0e61034f3145d66917970961c210 ("fs: relax mount_setattr() permission checks") in the kernel version that was being used. Above mitigation was discussed in email related to then-rejected CVE-2024-26821: https://lore.kernel.org/linux-cve-announce/2024051606-imaging-entrench-b327@gregkh/T/ After testing with qemuarm64 machine different linux-yocto versions, it was observed that the issue impacts following versions of currently supported LTS kernels: - 6.6.17 (fixed since 6.6.18 i.e. mount_setattr() returns 0) - 6.1.78 (fixed since 6.1.79 i.e. mount_setattr() returns 0) - 5.15.164 which is currently the newest of 5.15.y series (i.e. no known working version) Taking the above findings into consideration, add a new PACKAGECONFIG option removing which enables users to opt-out from using the feature which can cause issues with a bit older kernels. The option is enabled only for class-target here, since it otherwise causes following error during util-linux-native's do_configure task on Debian 11 build host (mountfd_api requirement fails): | configure: error: libmount_mountfd_support selected, but required mount FDs based API not available Versions 5.10.223, 5.4.279 and 4.10.317 were also tested with qemuarm64 but the issue was not reproduced with those versions - using strace showed that the mount_setattr call associated with the new mount API problem was not issued with these LTS kernel versions, which seemed to be confirmed also by following libmount debug message in these cases: 415: libmount: HOOK: [0x7fa115e818]: failed to init new API Note: In addition to the aforementioned, this change was tested also briefly using the current latest kernel versions 6.1.104, 6.6.45 and 6.10.3 that using the old mount API with newest kernels did not introduce any observable regression to the boot flow. (From OE-Core rev: dc086d9a8613143607af3583c72ed892e20b4d66) Signed-off-by: Niko Mauno Signed-off-by: Richard Purdie