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

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

2024-11-26T13:37:09+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: 2fa36487777ec352f5fb1379657236da342367a7) Signed-off-by: Alban Bedel Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit f8703b486a6ccf39225815362acadafb890ca56e) Signed-off-by: Steve Sakoman

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

util-linux: install lastlog2 volatile file

2024-07-21T10:08:11+00:00

Install lastlog2 volatile file to create /var/lib/lastlog directory to fix runtime error: $ 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: 0b651441363a6195a8d025f8010728bc42ae2ee5) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

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

2024-07-13T22:28:30+00:00

License-Update: =============== GPL-2.0 is changed to GPL-2.0-only in README.licensing. The following two patches are removed as they've been there in new release: 0001-login-utils-include-libgen.h-for-basename-API.patch mit-license.patch Other existing patches are refreshed to avoid patch-fuzz error. A new PACKAGECONFIG, lastlog2, is added, which serves as a switch to build Y2038 safe lastlog pam module. This is a new functionality added in 2.40. This 2.40.1 version has the problem of unnecessary remake, causing intermmittent errors at parallel make. The do_compile:prepend is a workaround for this. Upstream issue and PR are: https://github.com/util-linux/util-linux/issues/3061 https://github.com/util-linux/util-linux/pull/3064 do_install is changed to do_install:append, the legacy codes are removed. They've been there since the born of oe-core. I tested with ccache, there's no error. A new dependency, diffutils, is added to ptest. Because the mkswap-offset test case needs 'cmp' from diffutils. The tests/ts/misc/enosys test case is deleted for musl. This is because the test case is comparing error description output and that's libc specific. Results below can demonstrate the case. ''' root@qemux86-64:/usr/lib/util-linux/ptest# cat /usr/lib/util-linux/ptest/tests/expected/misc/enosys-ioctl test_enosys: ioctl r=0 errno=Success test_enosys: ioctl r=-1 errno=Function not implemented test_enosys: ioctl r=-1 errno=Inappropriate ioctl for device test_enosys: ioctl r=-1 errno=Inappropriate ioctl for device test_enosys: ioctl r=-1 errno=Function not implemented root@qemux86-64:/usr/lib/util-linux/ptest# cat /usr/lib/util-linux/ptest/tests/output/misc/enosys-ioctl test_enosys: ioctl r=0 errno=No error information test_enosys: ioctl r=-1 errno=Function not implemented test_enosys: ioctl r=-1 errno=Not a tty test_enosys: ioctl r=-1 errno=Not a tty test_enosys: ioctl r=-1 errno=Function not implemented ''' (From OE-Core rev: 2c5f70e7e73362502a7d8d0773fbd04520b26eef) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

recipes: Update WORKDIR references to UNPACKDIR

2024-05-02T14:15:51+00:00

Since we want to be able to stop unpacking to WORKDIR, correct the WORKDIR references in recipe do_compile/do_install tasks to use UNPACKDIR in the appropraite places instead. (From OE-Core rev: d73595df69667fe9d12ecd407b77a0b8dae2109c) Signed-off-by: Richard Purdie

shadow: install manpages

2024-04-23T12:40:24+00:00

Install the manpages for shadow, and also make the conflicting manpages alternatives in util-linux. (From OE-Core rev: 4b5a119ab36b2339b5469e5c7d34635090cc70f0) Signed-off-by: Daniel McGregor Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

util-linux: Set the license for util-linux-fcntl-lock to MIT

2024-04-04T13:05:03+00:00

This avoids problems if BSD-4-Clause is in INCOMPATIBLE_LICENSE since util-linux-fcntl-lock is now a dependency of run-postinsts. (From OE-Core rev: c2c7e1624e8080fb8fa1f14d252f20e85b232eb7) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

util-linux: Add fcntl-lock

2024-03-30T22:22:19+00:00

Add a version of flock that uses the fnctl based lockf locking instead of flock based locks. This allows us to take the same lock that opkg would use from a shell script. The two different locking mechanisms operate independently of each other. Inserting this C file into the util-linux build seems like the easiest/best place to insert the code. At this point it hasn't been discussed with upstream. (From OE-Core rev: d2b784110e2c3df8a0a41e4819cf2de9003f9fa3) Signed-off-by: Richard Purdie

util-linux: Add missing MIT license

2024-03-30T22:22:19+00:00

The MIT license was missing from the license list for util-linux. Add a patch, submitted to upstream which adds the missing license mentions. (From OE-Core rev: 24078c0542626f74c93203d17ab4b2bb2f9b5630) Signed-off-by: Richard Purdie