Closes systemd#15786.

(cherry picked from commit 50254f5)

Fixes systemd#15941.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22547

(cherry picked from commit 0e77fc6)

(cherry picked from commit c4473de)

Fixes systemd#15521.

(cherry picked from commit 9f83091)

This might fix systemd#15859, a bug which I find very puzzling.

(cherry picked from commit 75f6d5d)

(cherry picked from commit 132be2b)

Dropins may specify SourcePath= too, but we would do the stat only
after loading the main fragment, before loading of the drop-ins.

Fixes systemd#13634.

(cherry picked from commit c9e0695)

(cherry picked from commit 5aca2e6)

To make Driver= in [Match] section work in containers.

Note that ID_NET_DRIVER= property in udev database is set with the
result of the ethtool. So, this should not change anything for
non-container cases.

Closes systemd#15678.

(cherry picked from commit c643bda)

Based on an internal discussion whether emergency.target should remount disks
ro, or maybe remount them rw, or do nothing. In some cases people want to boot
ro, and always remounting rw would break that. In other cases, remounting disks
ro after they have already been mounted rw is mostly pointless and might even
not be possible. So let's just document that we don't change the state.

Also: any→other, since emergency.service *is* pulled in.

Also: just advertise "emergency" as the way to boot into the target.
We are not going to remove this option, and it's way easier to type than
"systemd.unit=emergency.target".

(cherry picked from commit 927b9b8)

Since this has been changed in: systemd@6e2f789, the change should be synchronized.

(cherry picked from commit 168561f)

…protocol provide an address

Before this, to speed up the system boot with IPv4 only network,
we need to specify `IPv6AcceptRA=no`, as it is enabled by default.

Closes systemd#15469.

(cherry picked from commit 3cd5924)

Fixes: 34437b4 ('sd-lldp: rework sd-lldp API')
(cherry picked from commit 9141594)

glibc 2.31 strips the AD flag, unless either the application specifies
RES_TRUSTAD or the options in resolv.conf contain trust-ad.

See https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=NEWS;hb=HEAD

(cherry picked from commit a742f98)

On my laptop (Lenovo X1carbo 4th) I very occasionally see test-boot-timestamps
fail with this tb:

262/494 test-boot-timestamps                    FAIL    0.7348453998565674 s (killed by signal 6 SIGABRT)

08:12:48 SYSTEMD_LANGUAGE_FALLBACK_MAP='/home/zbyszek/src/systemd/src/locale/language-fallback-map' SYSTEMD_KBD_MODEL_MAP='/home/zbyszek/src/systemd/src/locale/kbd-model-map' PATH='/home/zbyszek/src/systemd/build:/home/zbyszek/.local/bin:/usr/lib64/qt-3.3/bin:/usr/share/Modules/bin:/usr/condabin:/usr/lib64/ccache:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/zbyszek/bin:/var/lib/snapd/snap/bin' /home/zbyszek/src/systemd/build/test-boot-timestamps
--- stderr ---
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Failed to get SystemdOptions EFI variable, ignoring: Interrupted system call
Failed to read ACPI FPDT: Permission denied
Failed to read LoaderTimeInitUSec: Interrupted system call
Failed to read EFI loader data: Interrupted system call
Assertion 'q >= 0' failed at src/test/test-boot-timestamps.c:84, function main(). Aborting.

Normally it takes ~0.02s, but here there's a slowdown to 0.73 and things fail with EINTR.
This happens only occasionally, and I haven't been able to capture a strace.

It would be to ignore that case in test-boot-timestamps or always translate
EINTR to -ENODATA. Nevertheless, I think it's better to retry, since this gives
as more resilient behaviour and avoids a transient failure.

See
https://github.com/torvalds/linux/blob/master/fs/efivarfs/file.c#L75
and
torvalds/linux@bef3efb.

(cherry picked from commit 7229ec0)

…ions EFI var due to SecureBoot

Fixes: systemd#14864
(cherry picked from commit 484f4e5)

Fixup for 484f4e5. Should fix systemd#15730.

(cherry picked from commit a0fa268)

This should allow us to detect slowdowns caused by EFI variable read
access a bit.

(cherry picked from commit 698564d)

This is a safey net anyway, let's make it fully safe: if the data ends
on an uneven byte, then we need to complete the UTF-16 codepoint first,
before adding the final NUL byte pair. Hence let's suffix with three
NULs, instead of just two.

(cherry picked from commit c75e7da)

(cherry picked from commit d197c40)

(cherry picked from commit 8419064)

Quoting systemd#14828 (comment):

> [kernel uses] msleep_interruptible() and that means when the process receives
> any kind of signal masked or not this will abort with EINTR.  systemd-logind
> gets signals from the TTY layer all the time though.

> Here's what might be happening: while logind reads the EFI stuff it gets a
> series of signals from the TTY layer, which causes the read() to be aborted
> with EINTR, which means logind will wait 50ms and retry. Which will be
> aborted again, and so on, until quite some time passed. If we'd not wait for
> the 50ms otoh we wouldn't wait so long, as then on each signal we'd
> immediately retry again.

(cherry picked from commit eee9b30)

Cache it early in startup of the system manager, right after `/run/systemd` is
created, so that further access to it can be done without accessing the EFI
filesystem at all.

(cherry picked from commit 209b259)

(cherry picked from commit ce51632)

This allows disabling a few alternative ways to decode integers
formatted as strings, for safety reasons.

See: systemd#15991
(cherry picked from commit 707e93a)

Let's allow "-0" as alternative to "+0" and "0" when parsing integers,
unless the new SAFE_ATO_REFUSE_PLUS_MINUS flag is specified.

In cases where allowing the +/- syntax shall not be allowed
SAFE_ATO_REFUSE_PLUS_MINUS is the right flag to use, but this also means
that -0 as only negative integer that fits into an unsigned value should
be acceptable if the flag is not specified.

(cherry picked from commit c78eefc)

All other safe_atoXYZ_full() functions have the parameter optional,
let's make it optoinal here, too.

(cherry picked from commit aa85e4d)

Parsing is hard, hence let's use our own careful wrappers wherever
possible.

(cherry picked from commit c44702a)

Let's refuse "+" and "-" prefixed UIDs. Let's refuse whitespace-prefixed
UIDS, Let's refuse zero-prefixed UIDs. Let's be safe than sorry.

(cherry picked from commit f5979b6)

Coverity CID#1432701.

(cherry picked from commit 649bde8)
(cherry picked from commit 0046c58)

…gs]et_rcvbuf

In case the first getsockopt() call changes the value.

(cherry picked from commit 67f5ae2)
(cherry picked from commit 64d5848)

(cherry picked from commit 150c430)
(cherry picked from commit d08f6fd)

Otherwise a 'Before=remote-fs.target' dependency is added to the mount unit
which defeats the purpose of 'bg' option.

(cherry picked from commit e66d2ee)
(cherry picked from commit ad77a98)

By settings AI_ADDRCONFIG in hints we cannot for example resolve "localhost"
when the local machine only has a loopback interface. This seems like an
unnecessary restriction, drop it.

Inspired by https://bugzilla.redhat.com/show_bug.cgi?id=1839007.

(cherry picked from commit d0e5db4)
(cherry picked from commit 5e8bf33)

With this change, only manager_connect() in timesync.d uses AI_ADDRCONFIG. There
we are connecting to a remove server, so the flag is appropriate.

(cherry picked from commit 7e5f1d4)
(cherry picked from commit b0fff90)

RC_LOCAL_SCRIPT_PATH_START and RC_LOCAL_SCRIPT_PATH_STOP were was originally
added in the conversion to meson based on the autotools name. In
4450894 RC_LOCAL_SCRIPT_PATH_STOP was dropped.
We don't need to use such a long name.

(cherry picked from commit 452d2df)
(cherry picked from commit f2b9345)

Different systems use different paths for it and users are confused when the
man page has a path different than the one on the local system.

https://bugzilla.redhat.com/show_bug.cgi?id=1876905
(cherry picked from commit c2ee27a)
(cherry picked from commit 9353607)

(cherry picked from commit e29e5db)
(cherry picked from commit 1d17c00)

…ary arch

Let's suppress the secondary arch data, since we never ever want to
mount it if we found the primary arch.

Previously we only suppressed in the Verity case, but there's little
reason to entertain the idea of a secondary arch in non-Verity
environments either, we are not going to use them, and should not do
decryption or anything like that.

(cherry picked from commit 74cb2db)
(cherry picked from commit 418cf0e)

…at is true

(cherry picked from commit 3afda7c)
(cherry picked from commit 31875b3)

Let's verify that everything works the way we expect it to work, hence
check setsid() return code.

(cherry picked from commit efe4266)
(cherry picked from commit 6f9c8af)

(cherry picked from commit 2fef50c)
(cherry picked from commit f2763ff)

When exiting, let's explicitly wait for our worker processes to finish
first. That's useful if unmounting of /home/ is scheduled to happen
right after homed is down, as we then can be sure that the home
directories are properly unmounted and detached by the time homed is
fully terminated (otherwise it might happen that our worker gets killed
by the service manager, thus leaving the home directory and its backing
devices up/left for auto-clean which might be async).

Likely fixes systemd#16842

(cherry picked from commit 9796a9f)
(cherry picked from commit e1df274)

…ck-device is not supported

The directory backend needs a file system path, and not a raw block
device. That's only supported for the LUKS2 backend.

Let's make this clearer in the man page and also generate a better error
message if attempted anyway.

Fixes: systemd#17068
(cherry picked from commit f9d525a)
(cherry picked from commit a2a8802)

I happen to have a machine where /boot is not a separate mountpoint,
but rather just a directory under /. After upgrade to recent Fedora,
I found out that grub2 can't find any new kernels.

This happens because loadentry script generates kernel and initrd file
paths relative to /boot, while grub2 expects path to be relative to the
root of filesystem on which they are residing.

This commit fixes this issue by using stat's %m to find the mount point
of a partition holding the images, and using it as a prefix to be
removed from ENTRY_DIR_ABS.

Note that %m for stat requires coreutils 8.6, released in Oct 2010.

Signed-off-by: Kir Kolyshkin <[email protected]>
(cherry picked from commit 1cdbff1)
(cherry picked from commit 2ee1c57)

systemd-stable v245.8