Khem Raj [Mon, 26 Jul 2021 17:58:46 +0000 (10:58 -0700)]
networkd: Include linux/netdevice.h header
This header provides definitions for NET_NAME_UNKNOWN ånd NET_NAME_ENUM
Fixes build issue found with non-glibc systems
../git/src/network/networkd-link.c:1203:52: error: 'NET_NAME_UNKNOWN' undeclared (first use in this function)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit
2a0d07d6a0d5be63c6c10cb0789412f584858ec1)
(cherry picked from commit
369b2066e93e9a11fdfd3eb6fc7402ecd55fc7bd)
(cherry picked from commit
18e0b662ef9ea1e5f3d8c00a917b65af2d405de3)
(cherry picked from commit
5898d09e9b4d1c9034fa7e4fb88758ac141a7aea)
ratijas [Fri, 23 Jul 2021 10:32:52 +0000 (13:32 +0300)]
man: Fix incorrect EFI vendor UUID (last missing nibble)
(cherry picked from commit
d2e84b601805ae89cf8cb1b383b30c7c97cac73d)
(cherry picked from commit
595d9965bb07c1f96e159d5be31504972c9d0754)
(cherry picked from commit
aac6524cfdbd37878d2bad85f1c1b01a4ab04c64)
(cherry picked from commit
151c217ef207df1455c6b36e234356ec9767fc5c)
Cristian Rodríguez [Fri, 9 Jul 2021 21:19:05 +0000 (17:19 -0400)]
malloc() uses getrandom now
glibc master uses getrandom in malloc since https://sourceware.org/git/?p=glibc.git;a=commit;h=
fc859c304898a5ec72e0ba5269ed136ed0ea10e1 , getrandom should be in the default set so to avoid all non trivial programs to fallback to a PRNG.
(cherry picked from commit
14f4b1b568907350d023d1429c1aa4aaa8925f22)
(cherry picked from commit
1253d18af7449814bc882506b0fe3770311b3bc0)
(cherry picked from commit
38b7f010293a300a9ae4aa607c155ae916cdc828)
(cherry picked from commit
dc4550714061658daea5a11bfe7820f1a2c53630)
Zbigniew Jędrzejewski-Szmek [Wed, 23 Jun 2021 09:46:41 +0000 (11:46 +0200)]
basic/unit-name: do not use strdupa() on a path
The path may have unbounded length, for example through a fuse mount.
CVE-2021-33910: attacked controlled alloca() leads to crash in systemd and
ultimately a kernel panic. Systemd parses the content of /proc/self/mountinfo
and each mountpoint is passed to mount_setup_unit(), which calls
unit_name_path_escape() underneath. A local attacker who is able to mount a
filesystem with a very long path can crash systemd and the whole system.
https://bugzilla.redhat.com/show_bug.cgi?id=
1970887
The resulting string length is bounded by UNIT_NAME_MAX, which is 256. But we
can't easily check the length after simplification before doing the
simplification, which in turns uses a copy of the string we can write to.
So we can't reject paths that are too long before doing the duplication.
Hence the most obvious solution is to switch back to strdup(), as before
7410616cd9dbbec97cf98d75324da5cda2b2f7a2.
(cherry picked from commit
441e0115646d54f080e5c3bb0ba477c892861ab9)
(cherry picked from commit
764b74113e36ac5219a4b82a05f311b5a92136ce)
(cherry picked from commit
4a1c5f34bd3e1daed4490e9d97918e504d19733b)
(cherry picked from commit
b00674347337b7531c92fdb65590ab253bb57538)
duament [Sat, 17 Jul 2021 17:17:41 +0000 (01:17 +0800)]
shell-completion/zsh/_systemd-run: Fix completion of command names and arguments
(cherry picked from commit
3f49d1faf59acaa85aa5ad502c39b1a601d58d26)
(cherry picked from commit
b511a441f3277750e68a14d8d7e6649c4f182b86)
(cherry picked from commit
cb5564aea24d6d92716bdd0c06d1a2d7b91a1c71)
(cherry picked from commit
55f79382622187834113dcbce9166b778da3d62c)
Zbigniew Jędrzejewski-Szmek [Mon, 5 Jul 2021 19:29:11 +0000 (21:29 +0200)]
shared/format-table: allocate buffer of sufficient size
(cherry picked from commit
6dc57047ff0f1f9e98938ffb172dae06e6868b94)
(cherry picked from commit
e6407ca25852dadec355df2e6fdc92d1f189bceb)
(cherry picked from commit
d442b879abac5bcaf7756e53e304fd0ade36d49d)
(cherry picked from commit
4ac578db4afa08ced943cb5095d94992e0ac414c)
Zbigniew Jędrzejewski-Szmek [Wed, 7 Jul 2021 07:26:12 +0000 (09:26 +0200)]
NEWS: add old entry about Type=ether
Apparently it's an important feature for some folks:
https://utcc.utoronto.ca/\~cks/space/blog/linux/NetworkdMACMatchesWidely.
I think we considered this more of a bugfix, but it's somewhere on the border.
Let's add this it's easier to discover.
(cherry picked from commit
88b2a95064675c5f86648053cf124265f5289095)
(cherry picked from commit
3cb75aecc0a5facf2e057ea56d2334ebd3ee2761)
(cherry picked from commit
3f96f2a741e6f123b9f0a8dffed72eeea45dda78)
Zbigniew Jędrzejewski-Szmek [Tue, 6 Jul 2021 14:41:28 +0000 (16:41 +0200)]
tmpfiles: fix borked assert
It seems that fd_set_perms() is always called after checking that
fd >= 0 (also when called as action() in glob_item_recursively()),
so it seems that the assertion really came from fd==0.
Fixes #20140.
Also three other similar cases are updated.
(cherry picked from commit
b4b0f87c6275dde32769c2e75231caa1d4c21f9b)
(cherry picked from commit
1dcecfc50b6c4db3b76b81765403f84c06ecf225)
(cherry picked from commit
5f2d3e45aa156f5fe215c2fd609082423fdd6fc5)
Trent Piepho [Thu, 1 Jul 2021 19:19:57 +0000 (12:19 -0700)]
udev: Fix by-uuid symlink for ubifs volumes
ubifs volumes have a UUID and the built-in blkid is able to determine
it. The disk/by-uuid symlink isn't created because ubifs volumes are
not on block devices but on SUBSYSTEM="ubi" devices. See #20071.
Allow ubi subsystem devices to be processed by the persistent storage
rules too. The kernel device name matching already allows ubi* to pass.
The existing rules are sufficient to create the link.
The links look like other by-uuid symlinks, for example:
/dev/disk/by-uuid/
9a136158-585b-4ba4-9b70-
cbaf2cf78a1c -> ../../ubi0_1
(cherry picked from commit
21ac7884e9c1684d091d893254bcbe4b83740e9f)
(cherry picked from commit
15bd27b06c67e94541e3376d3d482f4f849f5aff)
(cherry picked from commit
01bd34c18ccb49b536c4d8ce7dac68e4e5893d4d)
Lennart Poettering [Thu, 1 Jul 2021 13:03:16 +0000 (15:03 +0200)]
Revert "rules: ubi mtd - add link to named partitions"
This reverts commit
7f1e9c806b6915e8020cf3706dc87e1cd37bc2fa, PR #6750
Apparently the rule change never worked, see #20071.
Fixes #20071
(cherry picked from commit
4b6bc397b454f79006481c1e8507d85c5bfd2e9a)
(cherry picked from commit
7e558b501783757f63b9c93edce43239a5178611)
(cherry picked from commit
897f14bf9d9fe7ab5482bf86a5efc9e2a1e9c831)
Zbigniew Jędrzejewski-Szmek [Thu, 1 Jul 2021 09:06:45 +0000 (11:06 +0200)]
core: add comment explaining event source deallocation
Followup for
bc989831e6. The original reproducer still works w/o the unref,
and doesn't work with this change.
(cherry picked from commit
13bb1ffb912cacea4041910e38674e0984ac5772)
(cherry picked from commit
d82da0f04f6ebe7044f4c33b9067c17c909a8d5d)
(cherry picked from commit
c15e100eec24e78bb78d4bd8c0b6ef6bdebc73d4)
Zbigniew Jędrzejewski-Szmek [Tue, 29 Jun 2021 07:10:42 +0000 (09:10 +0200)]
core: add default descriptions for slices
[ OK ] Created slice system-getty.slice (Slice /system/getty).
[ OK ] Created slice system-modprobe.slice (Slice /system/modprobe).
[ OK ] Created slice system-sshd\x2dkeygen.slice (Slice /system/sshd-keygen).
[ OK ] Created slice user.slice (User and Session Slice).
Before, the first three slices were shown without any description which didn't
look nice.
(cherry picked from commit
4dd21726f852010aef17e9b952b4bb1646fdf496)
(cherry picked from commit
0b0d80d96009e10ce36d683b7991829a2cfca67c)
(cherry picked from commit
3fa82957117677ec9d858bf86c203be6a39f812c)
Zbigniew Jędrzejewski-Szmek [Mon, 10 May 2021 11:12:53 +0000 (13:12 +0200)]
core/service: rework management of exec_fd event source
The code in service_spawn() was written as if exec_fd_event_source
was always unset. (We would either fail the assertion that is moved in the
patch, or leak the event source object if it was set.)
To make this work, let's always assert that exec_fd_event_source is unset,
and actually unset it service_sigchld_event(). I think this is the most
elegant approach. The problem is that we don't have the same information
about execution flags as in service_spawn(), so we need to conditionalize
on pid==main_pid to know if we should disable exec_fd_event_source.
I think this matches all cases where we may set exec_fd_event_source:
service_enter_start() and service_run_next_main().
service_enter_stop_post() calls service_set_state(), which will also destroy
the source. But that happens too late, because from service_enter_stop_post()
we call service_spawn() first, and then service_set_state() second.
(An alternative approach would be to deallocate the existing
exec_fd_event_source in service_spawn(). But this would mean that we would
temporarily have an event source attached to a process that we already know is
dead, which seems less than ideal.)
Original report from Dimitri John Ledkov <dimitri.ledkov@canonical.com>:
> Ubuntu private bug reference for this issue at the moment is
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
1921145
> Michael's and Ian's team run into an issue when using systemd in the
> initrd, without dbus daemon running, and launching a unit in a
> particular way that appears to lock up systemd (pid 1) it self.
> michael vogt: "The attached script works for me to reproduce this on
> classic. I tested 20.04 (245) and 21.04 (247) in a qemu VM. Sometimes
> I need to run it multiple times but usually it crashes after at most 2
> runs. Use "journalctl | tail" to see the messages, it's the same that
> Ian reported. There is also a /var/crash/_usr_lib_systemd_systemd
> crash file created."
> I understand that the particular way to run a unit is very odd,
> however, it is currently possible to invoke, and it would be expected
> for pid1 to not lock up and crash.
> The Assertion that systemd hits is along the lines of:
> [ 10.182627] systemd[1]: Assertion 's' failed at
> src/core/service.c:3204, function service_dispatch_exec_io().
> Aborting.
> [ 10.195458] systemd[1]: Caught <ABRT>, dumped core as pid 449.
> [ 10.204446] systemd[1]: Freezing execution.
(cherry picked from commit
bc989831e634123c2ff43bcbbeae19097ccc9ff9)
(cherry picked from commit
493c5c7bab9713afcd647dada885bed68b9d3cf3)
(cherry picked from commit
68fcea49fb630fe2475d6fb0220c9330c58e7c36)
Zbigniew Jędrzejewski-Szmek [Mon, 10 May 2021 08:22:07 +0000 (10:22 +0200)]
core: disable event sources before unreffing them
This mirrors the change done for systemd-resolved in
97935302283729c9206b84f5e00b1aff0f78ad19. Quoting that patch:
> We generally operate on the assumption that a source is "gone" as soon as we
> unref it. This is generally true because we have the only reference. But if
> something else holds the reference, our unref doesn't really stop the source
> and it could fire again.
In particular, we take temporary references from sd-event code, and when called
from an sd-event callback, we could temporarily see this elevated reference
count. This patch doesn't seem to change anything, but I think it's nicer to do
the same change as in other places and not rely on _unref() immediately
disabling the source.
(cherry picked from commit
5dcadb4c8320f6a7b8a9353404874d43668e4648)
(cherry picked from commit
67782e10f0dd0f2feeb036aa4380fa5c6c55aaea)
(cherry picked from commit
78578b31cd8fc3b6b8d76e5e9820a30cf3dc542a)
Alexander Tsoy [Mon, 28 Jun 2021 20:00:11 +0000 (23:00 +0300)]
resolved: do not try to copy empty NSEC types bitmaps
dns_resource_record_copy() assumes that NSEC types bitmap is non-empty
which results in a null pointer dereference inside bitmap_copy() in some
cases. Fix this by calling bitmap_copy() conditionally.
(cherry picked from commit
1f00a50c695fe3b55dee38fbd02a902a6c703c87)
(cherry picked from commit
fc7be6db131a5062dde76ee7857c2f91e1c402cb)
(cherry picked from commit
3422b16ef9a85ab0a31558a68db67f148961d4a1)
Zbigniew Jędrzejewski-Szmek [Wed, 23 Jun 2021 16:10:57 +0000 (18:10 +0200)]
dbus-socket: fix check of Listen* arguments
We checked the wrong field, which was always NULL here, so we would always
reject the assignment. We would also print the wrong string in the error
message:
$ sudo systemd-run --socket-property ListenFIFO=/tmp/fifo3 cat
Failed to start transient socket unit: Invalid socket path: FIFO
(cherry picked from commit
aeecab3804aae973577f36880af4b7799e4eb7d5)
(cherry picked from commit
78fb13b38572f6649f1e9822ef6acb8ca4952c12)
(cherry picked from commit
7bdc7ff0bb2d1dde1a81b2cbc76e424d1c50b7aa)
Mike Crowe [Thu, 24 Jun 2021 14:25:58 +0000 (15:25 +0100)]
resolvectl: Only strip ifname suffixes when being resolvconf
Only treat interface names containing dots specially when resolvectl is
pretending to be resolvconf to fix
https://github.com/systemd/systemd/issues/20014 .
Move the special suffix-stripping behaviour of ifname_mangle out to the
new ifname_resolvconf_mangle to be called from resolvconf only.
(cherry picked from commit
7875170f01991a1d28cfe284cc7075630cd69055)
(cherry picked from commit
6ec5680beaa8df4b4b87e9aa614d29561c0e98fe)
(cherry picked from commit
0d18f706a3816464053003b706bb6b2c27de12d1)
Andrea Pappacoda [Thu, 24 Jun 2021 15:30:51 +0000 (17:30 +0200)]
Lennart Poettering [Thu, 24 Jun 2021 11:13:39 +0000 (13:13 +0200)]
sd-journal: add missing bracket in journal verify log message
(cherry picked from commit
6abd991c718dbc1480ab7e71103a8b3e886bd3a3)
(cherry picked from commit
3dabd7f816fa0465c08745ce76f459c4c2a7c3d5)
(cherry picked from commit
912ae8fa70888747273d7226e9cc9a22c962dd8f)
Yu Watanabe [Wed, 23 Jun 2021 16:22:07 +0000 (01:22 +0900)]
sd-dhcp-client: tentatively ignore FORCERENEW command
This makes DHCP client ignore FORCERENEW requests, as unauthenticated
FORCERENEW requests causes a security issue (TALOS-2020-1142, CVE-2020-13529).
Let's re-enable this after RFC3118 (Authentication for DHCP Messages)
and/or RFC6704 (Forcerenew Nonce Authentication) are implemented.
Fixes #16774.
(cherry picked from commit
38e980a6a5a3442c2f48b1f827284388096d8ca5)
(cherry picked from commit
3ec1234d1e3195849088b2a3c70fbdefebeadc35)
(cherry picked from commit
f53d610144ca729a7e727fc6d3e86e3a4a2a53ed)
Luca Boccassi [Tue, 22 Jun 2021 13:56:19 +0000 (14:56 +0100)]
completion: fix 'unbound variables' errors
Fixes https://github.com/systemd/systemd/issues/19987
(cherry picked from commit
36ec026830c6978be8bd39f3c6d1d7822495e07f)
(cherry picked from commit
fe13c0bd40bc5ccdda61b8b474194920543a617b)
(cherry picked from commit
173d07a916f0a76a69b0ef4a26c0df5111cf9c70)
Luca Boccassi [Tue, 22 Jun 2021 13:55:22 +0000 (14:55 +0100)]
completion/systemd-delta,-resolve: autocomplete with parameters
(cherry picked from commit
6a0667d2b6f05682c2ced1b53132274049b9ea5c)
(cherry picked from commit
0aed618942b0bcc5946d15c91f3518fc5024789a)
(cherry picked from commit
b9b3d623fc919757d48f89394c0c325355eefde9)
Anders Wenhaug [Sun, 20 Jun 2021 19:43:07 +0000 (21:43 +0200)]
time-util: don't use plural units indiscriminately
format_timestamp_relative currently returns the plural form of
years and months no matter the quantity, and in many cases (for
durations > 1 week) this is the same with days.
This patch changes this so that the function takes the quantity into account,
returning "1 month 1 week ago" instead of "1 months 1 weeks ago".
(cherry picked from commit
45eb4d2261ed0d943fd503a6d79ee3b7b7558c09)
(cherry picked from commit
e74329ce9fa7ccb025960f9b220dff9e556a80e5)
(cherry picked from commit
f3f4ace8ea15ada14495a92b24e207769955b1e5)
Eric Cook [Wed, 16 Jun 2021 19:35:12 +0000 (15:35 -0400)]
shell-completion: revert
c1072f6473bafa063cbf700c86524083d2857031
fixing https://github.com/systemd/systemd/issues/19689
(cherry picked from commit
682e043c42fe3ac0fee4ce727458aaeb0e638589)
(cherry picked from commit
2683e7a16024506b203092208ca1d28b953a111a)
(cherry picked from commit
8e00d92fc27df97c1fe578c35c82e096d0aa1670)
Michal Koutný [Thu, 10 Jun 2021 13:58:43 +0000 (15:58 +0200)]
core: Avoid spurious realization of unit cgroups
Cgroups may be unnecessarily realized when they are not needed. This
happens, e.g. for mount units parsed from /proc/$PID/mountinfo, check
touch /run/ns_mount
unshare -n sh -c "mount --bind /proc/self/ns/net /run/ns_mount"
# no cgroup exists
file /sys/fs/cgroup/system.slice/run-ns_mount.mount
systemctl daemon-reload
# the vain cgroup exists
file /sys/fs/cgroup/system.slice/run-ns_mount.mount
. (Such cgroups can account to a large number with many similar mounts.)
The code already accounts for "lazy" realization (see various checks for
Unit.cgroup_realized) but the unit_deserialize() in the reload/reexec
path performs unconditional realization.
Invalidate (and queue) the units for realization only if we know that
they were already realized in the past. This is a safe thing to do even
in the case the reload brings some new cgroup setting (controllers, BPF)
because units that aren't realized will use the updated setting when the
time for their realization comes. (It's not even needed to add a code
comment because the current formulation suggests the changed behavior.)
(cherry picked from commit
cc815b7fea0ade5331e8dd22ef6b5183edb77608)
(cherry picked from commit
94f501805db8b272fd2d8d2c4eab0c5291db50e0)
(cherry picked from commit
8712fc5a181d1453840014d765c20c45dbf83b5f)
nl6720 [Thu, 10 Jun 2021 06:40:04 +0000 (09:40 +0300)]
kbd-model-map: add Latvian keyboard layout mapping
(cherry picked from commit
9dfb429a44b0c7e4c50f35f888ac8ba3c677a994)
(cherry picked from commit
9f7274055762c8ab31248489e7236c1a51154f62)
(cherry picked from commit
79f50bd61696e41fc45f31996ccafa2d7844cd81)
nerdopolis [Wed, 9 Jun 2021 13:00:02 +0000 (09:00 -0400)]
Clarify help information for --global
(cherry picked from commit
3c3335c7146a43137c46acfa18417cca101cb088)
(cherry picked from commit
12600fdc423c0d06906204795230314d5dbfde82)
(cherry picked from commit
aed5fb1dc7688bb1cc24d9845140782bcf554ba5)
Lennart Poettering [Tue, 8 Jun 2021 21:17:53 +0000 (23:17 +0200)]
journal: don't try to reuse already calculated hash between files with keyed hash feature
When suppressing duplicate fields between files we so far tried to reuse
the already known hash value of the data fields between files. This was
fine as long as we used the same hash function everywhere. However,
since addition of the keyed hash feature for journal files this doesn't
work anymore, since the hashes will be different for different files.
Fixes: #19172
(cherry picked from commit
2e1a8a5dab8b5519c079c9bed54fc682aa4095b0)
(cherry picked from commit
d804bcadcb448879f31c32363970d9b70b742b9a)
(cherry picked from commit
0f110a75efb789d131ec96cbc4967b7fb1b1d628)
Lennart Poettering [Tue, 8 Jun 2021 20:14:40 +0000 (22:14 +0200)]
journal: add some careful overflow checking
(cherry picked from commit
d8671b1c6f036ce270b9631973314e7de24e74b1)
(cherry picked from commit
84e1819ec104a168f7904134b6212669133c955f)
(cherry picked from commit
03af9b1476ff56c67cb84d14927f1ac7b1a534e3)
Lennart Poettering [Wed, 9 Jun 2021 09:56:00 +0000 (11:56 +0200)]
seccomp: add some recently added syscalls to filter groups
(cherry picked from commit
34254e599a28529bdb89f91571adeaf7c76d9f43)
(cherry picked from commit
daaf9273294f133ab9c970b3172608686de6f86a)
(cherry picked from commit
e2950d261dd45fa039ed8f305bf869d65a966cec)
Yu Watanabe [Tue, 8 Jun 2021 01:23:47 +0000 (10:23 +0900)]
core/socket: do not assign another fd to SocketPort which already has a fd on deserialization
Otherwise, if a socket address is duplicated, then the previous fd is
closed.
Fixes #19843.
(cherry picked from commit
3da0caf5bbf3c8cab716c4d7adf0eb25907dc951)
(cherry picked from commit
11acee8a00f1e04952f86088078041849d8f9819)
(cherry picked from commit
1f5600df9cf5c3dcd4b4ff822e2de916d137e5e2)
Lennart Poettering [Mon, 7 Jun 2021 14:08:45 +0000 (16:08 +0200)]
udevadm: fix --tag-match help + description
(cherry picked from commit
d27e6aee5050da17bc9531fb62ac11aba4b15ceb)
(cherry picked from commit
98af14bf53e0aeebf9d88b8f1c202a31ae7bb753)
(cherry picked from commit
e8e2c93ed92b6cace68a4fd46bb6d6404a4f1353)
Zbigniew Jędrzejewski-Szmek [Tue, 1 Jun 2021 06:05:03 +0000 (08:05 +0200)]
units: stop automount unit when shutting down
This is currently our only .automount unit. We wouldn't want to trigger it
accidentally during shutdown, so let's stop it too.
(cherry picked from commit
dc16846c26287fd2081eb3c4a73487c9b186e2b7)
(cherry picked from commit
b1ce5653fac2766c4b4a070fec2126f211d49efa)
(cherry picked from commit
9a8023994ef873dcb2f27ce0a00f7ac9e5248fc2)
Franck Bui [Fri, 28 Aug 2020 14:03:06 +0000 (16:03 +0200)]
pid1: only add a Wants= type dependency on /tmp when PrivateTmp=yes
We support that tmp.mount being masked, and this should not be considered an
error.
(cherry picked from commit
b2c7d1bbc2243a425d9b825859bbd0647eecd050)
(cherry picked from commit
6a3a8c70686ab6da80dd87d0bd816a8c18980b71)
(cherry picked from commit
8d8b959cd418f1f91550c7ff5578bfc5af16dbd0)
Zbigniew Jędrzejewski-Szmek [Wed, 2 Jun 2021 13:44:29 +0000 (15:44 +0200)]
tmpfiles: do not check if unresolved globs are autofs paths
With the previous commit, we would not complain about the not-found path, but
the check is still not useful. We use a libc function to resolve the glob, and
it has no notion of treating autofs specially. So we can't avoid touching
autofs when resolving globs. But usually the glob is found in the last
component of the path, so if we strip the glob part, we can still do a useful
check in many cases. (E.g. if /var/tmp is on autofs, something like
"/var/tmp/<glob>" is much more likely than "/var/<glob-that-matches-tmp>/<something>".)
With the system config in F34, we check the following prefixes:
/var/tmp/abrt/* → /var/tmp/abrt/
/run/log/journal/
08a5690a2eed47cf92ac0a5d2e3cf6b0/*.journal* → /run/log/journal/
08a5690a2eed47cf92ac0a5d2e3cf6b0/
/var/lib/systemd/coredump/.#core*.
21e5c6c28c5747e6a4c7c28af9560a3d* → /var/lib/systemd/coredump/
/tmp/podman-run-* → /tmp/
/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-*/tmp → /tmp/
/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-* → /tmp/
/tmp/containers-user-* → /tmp/
/var/tmp/beakerlib-* → /var/tmp/
/var/tmp/dnf*/locks/* → /var/tmp/
/var/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-*/tmp → /var/tmp/
/var/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-* → /var/tmp/
/var/tmp/abrt/* → /var/tmp/abrt/
/var/tmp/beakerlib-* → /var/tmp/
/var/tmp/dnf*/locks/* → /var/tmp/
/tmp/podman-run-* → /tmp/
/tmp/containers-user-* → /tmp/
/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-* → /tmp/
/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-*/tmp → /tmp/
/var/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-* → /var/tmp/
/var/tmp/systemd-private-
21e5c6c28c5747e6a4c7c28af9560a3d-*/tmp → /var/tmp/
/var/lib/systemd/coredump/.#core*.
21e5c6c28c5747e6a4c7c28af9560a3d* → /var/lib/systemd/coredump/
/run/log/journal/
08a5690a2eed47cf92ac0a5d2e3cf6b0/*.journal* → /run/log/journal/
08a5690a2eed47cf92ac0a5d2e3cf6b0/
(cherry picked from commit
bd6d28f21ad212e141b5e74bd0b7ad517f64a711)
(cherry picked from commit
399a00be3536cb5fbf3f96058c2a88a2a634d466)
(cherry picked from commit
4a78d0a80fe0eaf8bc0d6579ef96bb31e6afaf48)
Zbigniew Jędrzejewski-Szmek [Wed, 2 Jun 2021 14:01:40 +0000 (16:01 +0200)]
basic/glob-util: add helper to strip the glob part from a glob
(cherry picked from commit
1e472a6ce4747a1f10954fb239df73580c8e7411)
(cherry picked from commit
82fcf663cf2cec519185330964c9fdee956047d8)
(cherry picked from commit
ae2ff72e34bf21d3d3e70dbfbe585470d18912ed)
Zbigniew Jędrzejewski-Szmek [Wed, 2 Jun 2021 13:40:27 +0000 (15:40 +0200)]
tmpfiles: stop complaining about autofs on not-found paths
systemd-tmpfiles[328]: Failed to determine whether '/run/cryptsetup' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/etc/resolv.conf' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/lock/subsys' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/setrans' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/console' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/faillock' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/sepermit' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/motd.d' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/motd.d' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/motd' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/run/nologin' is below autofs, ignoring: No such file or directory
systemd-tmpfiles[328]: Failed to determine whether '/var/lib/systemd/pstore' is below autofs, ignoring: No such file or directory
... and so on and so on.
(cherry picked from commit
16eff8271b402f2705d4329fa4cf5a0435e65996)
(cherry picked from commit
a2861e9b9c60bb697854a1aa317c0c365204aab1)
(cherry picked from commit
eafd9394b0d4ad6bf5b72f2959a0c54e319189e5)
Lennart Poettering [Wed, 2 Jun 2021 13:49:10 +0000 (15:49 +0200)]
pid1: don't choke on overly long device paths
This mimics what we do for device units: if there's a device we cannot
synthesize a good swap unit name for, then proceed without failure.
(cherry picked from commit
e82c6e8b6230b237c838f053d52baa3297668eaa)
(cherry picked from commit
5fbb002c65c5dbfb9e789caf3bea1dc6e63ee7ae)
(cherry picked from commit
0049b74fb7eeb275992f6a129d90fff82b7f3a9f)
Lennart Poettering [Wed, 2 Jun 2021 13:29:29 +0000 (15:29 +0200)]
pid1: reduce log noise generated by devices with overly long sysfs paths
This basically does what
2c905207db37c691d4abef868165ad5ea2dd0f4f did
for mount units
Fixes: #16161
(cherry picked from commit
ad172d19d5ef8b5a3631a8484cc3d1a28dba26c2)
(cherry picked from commit
7f035c549fdc0660431d48f1f7dcb7fc41bad22c)
(cherry picked from commit
8a20311c6d145b0d6738a54d827b9df0b34f187e)
Yu Watanabe [Wed, 2 Jun 2021 20:55:05 +0000 (05:55 +0900)]
efi: drop glibc header and use pre-defined macros
This reverts
72dc626b3d6905b105ae61ca2c60f51a6f74070e and replace glibc
specific macros with compiler's pre-defined macros.
(cherry picked from commit
ffc36c276c47a9b3f21e83947090f11039628676)
(cherry picked from commit
cab22cae2addcbfaa42621440bd7cb4b1a56c84f)
(cherry picked from commit
1733a1fbb6aa30531445145f2b0e761c8363ba7d)
Yu Watanabe [Wed, 2 Jun 2021 07:29:59 +0000 (16:29 +0900)]
sd-device: do not use ::subsystem member directly
The value is set dynamically when sd_device_get_subsystem() is called
first time.
Fixes the following issue:
```
$ build/udevadm test /sys/class/block/dm-1
...
Assertion '_subsystem' failed at src/libsystemd/sd-device/sd-device.c:767, function device_set_subsystem(). Aborting.
Program received signal SIGABRT, Aborted.
```
(cherry picked from commit
2255e8adee37c490bf8cf2daab791b6f746bb0a0)
(cherry picked from commit
93cf1abc60b774eb5c19e327a2079f67e80011df)
(cherry picked from commit
5930ef617350614df5cb71df8c66c54b0b2fa74a)
Zbigniew Jędrzejewski-Szmek [Tue, 1 Jun 2021 15:40:51 +0000 (17:40 +0200)]
various: don't say that the timestamp 'changed' on initial load
I always found this a bit annoying.
With the patch:
$ SYSTEMD_LOG_LEVEL=debug build/udevadm test /sys/class/block/dm-1
...
Loaded timestamp for '/etc/systemd/network'.
Loaded timestamp for '/usr/lib/systemd/network'.
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/10-eth0.link
Created link configuration context.
Loaded timestamp for '/etc/udev/rules.d'.
Loaded timestamp for '/usr/lib/udev/rules.d'.
...
(cherry picked from commit
0d5a24beaedb161d4f7fe07361d2a5abdbd6e736)
(cherry picked from commit
688b311f5c6c0b20a3811f6a135bf87e11f36502)
(cherry picked from commit
c2592a1b81eade894c28dbe874c0ca3d4cb81002)
Zbigniew Jędrzejewski-Szmek [Tue, 1 Jun 2021 08:00:01 +0000 (10:00 +0200)]
varlink: remove duplicated "varlink:" prefix
We had:
systemd[1]: varlink-36: New incoming message: {"method":"io.systemd.UserDatabase.GetMemberships","parameters":{"userName":"gdm","service":"io.systemd.DynamicUser"},"more":true}
systemd[1]: varlink-36: varlink: changing state idle-server → processing-method-more
systemd[1]: varlink-36: Sending message: {"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
systemd[1]: varlink-36: varlink: changing state processing-method-more → processed-method
systemd[1]: varlink-36: varlink: changing state processed-method → idle-server
systemd[1]: varlink-36: Got POLLHUP from socket.
systemd[1]: varlink-36: varlink: changing state idle-server → pending-disconnect
systemd[1]: varlink-36: varlink: changing state pending-disconnect → processing-disconnect
systemd[1]: varlink-36: varlink: changing state processing-disconnect → disconnected
So let's drop the "varlink:" prefix and use capitalized sentences like in other messages.
(cherry picked from commit
953394e3bb1f1ead3c1d80237b97b71835b0755a)
(cherry picked from commit
780768328a755057f955f36bac56e1da01e090f0)
(cherry picked from commit
b80573f32b6c2c63e3f159d444c1b607401ae695)
Zbigniew Jędrzejewski-Szmek [Tue, 1 Jun 2021 07:55:09 +0000 (09:55 +0200)]
varlink: say "varlink:" instead of "n/a:" when no description is available
For new connections, we log something like this:
systemd[1]: n/a: New incoming connection.
systemd[1]: n/a: Connections of user 997: 0 (of 1024 max)
systemd[1]: varlink-22: varlink: setting state idle-server
systemd[1]: varlink-22: New incoming message: ...
This "n/a" is not very pretty, and without context it would be hard to even
figure out this is a varlink connection.
(cherry picked from commit
f35e9b101d80c05d5a5eaece6e62e8eeb5743691)
(cherry picked from commit
b5691dd6f83d99e0588532940c1c24e5647662f7)
(cherry picked from commit
f6203648f2e1231549da61ba63a3c92b398411b4)
Yu Watanabe [Wed, 2 Jun 2021 10:10:49 +0000 (19:10 +0900)]
udev: ignore the case that the device is already removed
See #19788.
(cherry picked from commit
6be1feb1d7e30c0e7591121b74d4c3c7079de6b3)
(cherry picked from commit
b4ad8b418f65e8fbe8719344415758e6e62602f6)
(cherry picked from commit
20d8495281acfe0f202bb2fed0e1acb3e0d7438d)
Yu Watanabe [Wed, 2 Jun 2021 06:38:29 +0000 (15:38 +0900)]
efi: include endian.h to handle endian correctly
The macro __BYTE_ORDER__ is defined in endian.h.
(cherry picked from commit
72dc626b3d6905b105ae61ca2c60f51a6f74070e)
(cherry picked from commit
326e3ae2af0254c0d489ee053610fbbdc60a1f8b)
(cherry picked from commit
cebb255e6afec63bcd6ba9ec1d2c9718b54ffc8a)
Yu Watanabe [Wed, 2 Jun 2021 06:36:26 +0000 (15:36 +0900)]
efi: do not use _STRING_ARCH_unaligned macro
It is already removed from glibc. See,
https://sourceware.org/git/?p=glibc.git;a=commit;h=
16396c41deab45f715ffd813280d9d685b3b281e
https://sourceware.org/git/?p=glibc.git;a=commit;h=
09a596cc2cf4e0f9f8e9f3bba4b1a97efcb13bcb
(cherry picked from commit
959ab90bbc08855ad5824efecbc03d37b3f9c982)
(cherry picked from commit
d31347080272128e9b5c5f922a3f098ba62b059e)
(cherry picked from commit
dcc23771b0c9f05330f14fe995a96964d3672004)
Lennart Poettering [Tue, 1 Jun 2021 20:26:49 +0000 (22:26 +0200)]
mount: be more descriptive when logging about overly long mount point paths
This is prompted by #17684: let's very explicitly say that the name is
too long for us, and that we'll ignore it.
(cherry picked from commit
3ebc9b9b30b04a3aeec55a11022b337ec5fdb5cf)
(cherry picked from commit
264f179b692843fbb5de2e111b85e6e8bb837e68)
(cherry picked from commit
71b879ad15cbd5d76d1006cce44757de780165cd)
Lennart Poettering [Tue, 1 Jun 2021 20:20:55 +0000 (22:20 +0200)]
core: when looping over mount/swap names, continue if we find one which doesn't translate to a valid unit name
(cherry picked from commit
598a6a8491abd311d36b11caf262123fbbffb2c0)
(cherry picked from commit
f564342089ab56e44bf7240d19b860f2ed003e58)
(cherry picked from commit
ed9ab6a264d3dfb344b233e32269d46ae83f75d3)
Lennart Poettering [Tue, 1 Jun 2021 17:43:55 +0000 (19:43 +0200)]
unit-name: generate a clear error code when converting an overly long fs path to a unit name
(cherry picked from commit
9d5acfab20c5f1177d877d0bec18063c0a6c5929)
(cherry picked from commit
1579dce2c2a162bb09afb9a8a46fd4f7e8fbf1d5)
(cherry picked from commit
0488b743e9c6ab1e885933eebda4ba9232003a2a)
Zbigniew Jędrzejewski-Szmek [Tue, 1 Jun 2021 14:17:16 +0000 (16:17 +0200)]
pam: do not require a non-expired password for user@.service
Without this parameter, we would allow user@ to start if the user
has no password (i.e. the password is "locked"). But when the user does have a password,
and it is marked as expired, we would refuse to start the service.
There are other authentication mechanisms and we should not tie this service to
the password state.
The documented way to disable an *account* is to call 'chage -E0'. With a disabled
account, user@.service will still refuse to start:
systemd[16598]: PAM failed: User account has expired
systemd[16598]: PAM failed: User account has expired
systemd[16598]: user@1005.service: Failed to set up PAM session: Operation not permitted
systemd[16598]: user@1005.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
systemd[1]: user@1005.service: Main process exited, code=exited, status=224/PAM
systemd[1]: user@1005.service: Failed with result 'exit-code'.
systemd[1]: Failed to start user@1005.service.
systemd[1]: Stopping user-runtime-dir@1005.service...
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=
1961746.
(cherry picked from commit
71889176e4372b443018584c3520c1ff3efe2711)
(cherry picked from commit
0af5a8921f6019dc35057482711f0fbe347b0c06)
(cherry picked from commit
050dd460e83ca10b56b11533a60b6a5f40d42203)
Lennart Poettering [Tue, 1 Jun 2021 14:46:40 +0000 (16:46 +0200)]
logind-dbus: correctly calculate when to create /etc/nologin file in all cases
Fixes: #19258
(cherry picked from commit
cbb6c000c7f08f97fca28db990cd6aeb7aad7f4a)
(cherry picked from commit
e55a705af5bfe53c754727138455599798a573bf)
(cherry picked from commit
270716d95ad5c4838de8d344400e2f234ab30e29)
Yu Watanabe [Fri, 28 May 2021 10:48:33 +0000 (19:48 +0900)]
basic/unit-file: fix use-after-free
This fixes a bug introduced by
e8630e695232bdfcd16b55f3faafb4329c961104.
Fixes CID#
1453292.
(cherry picked from commit
7f1238bd04000f3333e8e2fcb82c9c6e18ee3ffc)
(cherry picked from commit
218117da2a8b4f1eccfc61353fdbe01219696378)
(cherry picked from commit
5c86f9e0381dadc06650492cd68b28ed800d376d)
Yu Watanabe [Tue, 25 May 2021 20:02:18 +0000 (05:02 +0900)]
core/service: do not set zero error to log_unit_debug_errno()
Fixes #19725.
(cherry picked from commit
95599cacd3944073f7d944a8b3973e1308d1d57f)
(cherry picked from commit
1af2dba1d3d2d6ffba6816d8ff59eb034074cc18)
(cherry picked from commit
13426b7801116cd706b0b0fed8237c6e43ad9dfd)
Mantas Mikulėnas [Tue, 25 May 2021 10:09:05 +0000 (13:09 +0300)]
README: point at IRC channel on the new network
(cherry picked from commit
fb906b00c68e34b8692e207a658bcfa3df62456c)
(cherry picked from commit
2aefb7beff0601c8785625784ace2f0d93214321)
(cherry picked from commit
6eeeaa533ad4aa86540af2abb79798c45f05370d)
Lennart Poettering [Fri, 14 May 2021 16:20:32 +0000 (18:20 +0200)]
systemctl: re-align colon in status output
(cherry picked from commit
1d406dceb769da2123417e6a06c85a99ebead7b1)
(cherry picked from commit
409c6a89e475e05776003cd43cb032050b6efa1e)
(cherry picked from commit
ff298cffcce97c8976a0912ec518a7ffbc6425e2)
Zbigniew Jędrzejewski-Szmek [Mon, 24 May 2021 20:49:56 +0000 (22:49 +0200)]
systemctl: avoid crash when pattern expands to empty unit list
Fixes #19652.
(cherry picked from commit
ffcd68385226d4b499dbff0123271e1d3fb8f516)
(cherry picked from commit
9a24f5edcc1c16f2afaa943dfd39f413322a5a0a)
(cherry picked from commit
ec52cddcce818b0033469ebbe40a500cd83d2664)
наб [Tue, 16 Mar 2021 15:59:07 +0000 (16:59 +0100)]
kernel-install: don't erase previous errors if a hook returns 77
The manpage says that exiting 77 is the same as exiting 0,
then skipping all other hooks, but the behaviour heretofor
was to exit 0, skip all, and behave as if all hooks exited 0
(cherry picked from commit
44230fa2b050d63fce49b4bfbbb93c42940754cc)
(cherry picked from commit
954f6ae49a6dc8a7994ff7ca3c86551a8748c2d1)
(cherry picked from commit
68ccbef7f0c6b6a81e5d8ad21f1ab9618e3000c5)
Roshan Shariff [Mon, 24 May 2021 07:30:38 +0000 (01:30 -0600)]
rules.d: Properly quote $env{MODALIAS}
Add quotes around use of $env{MODALIAS} in rules.d/80-drivers.rules. The
modalias can contain whitespace, for example when it is dynamically generated
using device or vendor IDs.
(cherry picked from commit
07c0e5eeaf3183963f4d680555d2289a33735d6e)
(cherry picked from commit
1151d6f55dd5cc4925a52e0faeca98963114df9b)
(cherry picked from commit
219710d990e5ea8add3819aa239e15d13e518b04)
Luca Boccassi [Thu, 20 May 2021 09:35:36 +0000 (10:35 +0100)]
journal: fix uninitialized variable use
If the journal file being processed is archivied, seqnum_id will not be
initialized before being passed on, and coverity complains.
Initialize it to zero.
CID #
1453235
(cherry picked from commit
06a368e8198a9cbfad86ba17bba6a76a33f15492)
(cherry picked from commit
b97c113704056c386574c047928e410c6c1e89ae)
(cherry picked from commit
f7b76d56968811b5ee7951f9d29261748c81a337)
Yu Watanabe [Thu, 20 May 2021 07:14:17 +0000 (16:14 +0900)]
network: fix an infinite loop
Fixes #19467.
(cherry picked from commit
e8f99f4e249916e12c09ee5cc9a108cba6a2b5c0)
(cherry picked from commit
b234ee7859de556c272c36fc691cee4cb08f7230)
(cherry picked from commit
a4a7a90a79b6bb379ac8bb9c637e5df3d18b9341)
Franck Bui [Wed, 19 May 2021 08:18:21 +0000 (10:18 +0200)]
kbd-model-map: add mapping 'es-dvorak'
And update test-keymap-util accordingly.
While at it, make sure to use tabs everywhere.
(cherry picked from commit
0495728429096a405b1d2cf1fa283a90c30ebaa9)
(cherry picked from commit
644a8ca3e026d22e71cb1f37034e6713bb8ee982)
(cherry picked from commit
b47bc5bd13e79dde173740d894c6d06d596c1003)
ei-ke [Sun, 16 May 2021 16:12:12 +0000 (18:12 +0200)]
Lennart Poettering [Fri, 5 Mar 2021 16:47:45 +0000 (17:47 +0100)]
dns-query: export CNAME_MAX, so that we can use it in other files, too
Let's rename it a bit, to be more explanatory while exporting it.
(And let's bump the CNAME limit to 16 — 8 just sounded so little)
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=
1949670.
(cherry picked from commit
e0ae456a554d0fce250f9a009c561b97f20c41f8)
(cherry picked from commit
0e1e59674da060af421aed4f2a6a97b899e20054)
Zbigniew Jędrzejewski-Szmek [Fri, 14 May 2021 08:49:24 +0000 (10:49 +0200)]
resolved: fix braino with reference counting and linked lists
In
0e0fd08fc832b8f42e567d722d388eba086da5ff I added reference counts to keep
track of the DnsQueryCandidate objects. Unfortunately, dns_query_unref_candidates()
was written as
while (q->candidates)
dns_query_candidate_unref(q->candidates);
i.e. it would keep dropping the reference count as many times as needed for it
to hit 0, making the patch less than fully effective.
dns_query_unref_candidates() is renamed to dns_query_detach_candidates() and
changed to drop exactly one reference from each of the linked candidates.
Example failure:
==463== Invalid read of size 8
==463== at 0x419C93: dns_query_candidate_go (resolved-dns-query.c:159)
==463== by 0x41A143: dns_query_candidate_notify (resolved-dns-query.c:304)
==463== by 0x434BD6: dns_transaction_complete (resolved-dns-transaction.c:437)
==463== by 0x436A0F: dns_transaction_process_dnssec (resolved-dns-transaction.c:976)
==463== by 0x4378C1: dns_transaction_process_reply (resolved-dns-transaction.c:1387)
==463== by 0x437CE9: on_dns_packet (resolved-dns-transaction.c:1444)
==463== by 0x4B2DC9B: source_dispatch (sd-event.c:3512)
==463== by 0x4B2FB1F: sd_event_dispatch (sd-event.c:4077)
==463== by 0x4B2FFFA: sd_event_run (sd-event.c:4138)
==463== by 0x4B301D6: sd_event_loop (sd-event.c:4159)
==463== by 0x464A24: run (resolved.c:92)
==463== by 0x464B3C: main (resolved.c:99)
==463== Address 0x5f409d0 is 32 bytes inside a block of size 72 free'd
==463== at 0x48410E4: free (vg_replace_malloc.c:755)
==463== by 0x418EDF: mfree (alloc-util.h:48)
==463== by 0x4197E8: dns_query_candidate_free (resolved-dns-query.c:67)
==463== by 0x4198B7: dns_query_candidate_unref (resolved-dns-query.c:70)
==463== by 0x41A2E3: dns_query_unref_candidates (resolved-dns-query.c:337)
==463== by 0x41C5FE: dns_query_cname_redirect (resolved-dns-query.c:1028)
==463== by 0x41CA04: dns_query_process_cname_one (resolved-dns-query.c:1128)
==463== by 0x41CA80: dns_query_process_cname_many (resolved-dns-query.c:1157)
==463== by 0x40C0BD: bus_method_resolve_hostname_complete (resolved-bus.c:198)
==463== by 0x41B312: dns_query_complete (resolved-dns-query.c:562)
==463== by 0x41C1AC: dns_query_accept (resolved-dns-query.c:922)
==463== by 0x41C2C4: dns_query_ready (resolved-dns-query.c:955)
==463== by 0x41A162: dns_query_candidate_notify (resolved-dns-query.c:314)
==463== by 0x434BD6: dns_transaction_complete (resolved-dns-transaction.c:437)
==463== by 0x438995: dns_transaction_prepare (resolved-dns-transaction.c:1728)
==463== by 0x43921D: dns_transaction_go (resolved-dns-transaction.c:1928)
==463== by 0x419C7C: dns_query_candidate_go (resolved-dns-query.c:163)
==463== by 0x41A143: dns_query_candidate_notify (resolved-dns-query.c:304)
==463== by 0x434BD6: dns_transaction_complete (resolved-dns-transaction.c:437)
==463== by 0x436A0F: dns_transaction_process_dnssec (resolved-dns-transaction.c:976)
==463== by 0x4378C1: dns_transaction_process_reply (resolved-dns-transaction.c:1387)
==463== by 0x437CE9: on_dns_packet (resolved-dns-transaction.c:1444)
==463== by 0x4B2DC9B: source_dispatch (sd-event.c:3512)
==463== by 0x4B2FB1F: sd_event_dispatch (sd-event.c:4077)
==463== by 0x4B2FFFA: sd_event_run (sd-event.c:4138)
==463== by 0x4B301D6: sd_event_loop (sd-event.c:4159)
==463== by 0x464A24: run (resolved.c:92)
==463== by 0x464B3C: main (resolved.c:99)
==463== Block was alloc'd at
==463== at 0x483E86F: malloc (vg_replace_malloc.c:380)
==463== by 0x418F81: malloc_multiply (alloc-util.h:96)
==463== by 0x419378: dns_query_candidate_new (resolved-dns-query.c:23)
==463== by 0x41B42C: dns_query_add_candidate (resolved-dns-query.c:582)
==463== by 0x41BB7A: dns_query_go (resolved-dns-query.c:762)
==463== by 0x40CE3A: bus_method_resolve_hostname (resolved-bus.c:464)
==463== by 0x4A84B86: method_callbacks_run (bus-objects.c:414)
==463== by 0x4A87961: object_find_and_run (bus-objects.c:1323)
==463== by 0x4A87FEE: bus_process_object (bus-objects.c:1443)
==463== by 0x4AA3434: process_message (sd-bus.c:2964)
==463== by 0x4AA3623: process_running (sd-bus.c:3006)
==463== by 0x4AA4110: bus_process_internal (sd-bus.c:3226)
==463== by 0x4AA41EF: sd_bus_process (sd-bus.c:3253)
==463== by 0x4AA5343: io_callback (sd-bus.c:3604)
==463== by 0x4B2DC9B: source_dispatch (sd-event.c:3512)
==463== by 0x4B2FB1F: sd_event_dispatch (sd-event.c:4077)
==463== by 0x4B2FFFA: sd_event_run (sd-event.c:4138)
==463== by 0x4B301D6: sd_event_loop (sd-event.c:4159)
==463== by 0x464A24: run (resolved.c:92)
==463== by 0x464B3C: main (resolved.c:99)
Fixes #19376.
(cherry picked from commit
c856ef0457c35e9edfdbf085b69ec81c126d48e5)
(cherry picked from commit
89324e233eef767334d9bfe5eed96956c973c2ad)
(cherry picked from commit
c8d7fab2286384b19ff6328cece107c4c02d7bb8)
tramsay [Mon, 5 Apr 2021 22:12:49 +0000 (17:12 -0500)]
network:dhcp4_server_configure returns if not able to get timezone
When /etc/localtime is a symbolic link pointing to another symbolic
link, get_timezone will return -EINVAL instead of the timezone.
This issue can cause systemd-networkd DHCPServer to fail.
Instead of returning failure, log a warning indicating that that
the timezone will not be sent.
modified: networkd-dhcp-server.c
(cherry picked from commit
7b5018ca9e6d3279887ec7113818f41d5b831c4d)
(cherry picked from commit
37c4cfde0ce613f0f00544d3f4e2e72bf93d9c76)
(cherry picked from commit
db85ea172f9b4e6cd2f46bffd63164a09404001f)
Zbigniew Jędrzejewski-Szmek [Fri, 14 May 2021 12:16:17 +0000 (14:16 +0200)]
meson: call find_program() once and reuse the variable everywhere
Meson 0.58 has gotten quite bad with emitting a message every time
a quoted command is used:
Program /home/zbyszek/src/systemd-work/tools/meson-make-symlink.sh found: YES (/home/zbyszek/src/systemd-work/tools/meson-make-symlink.sh)
Program sh found: YES (/usr/bin/sh)
Program sh found: YES (/usr/bin/sh)
Program sh found: YES (/usr/bin/sh)
Program sh found: YES (/usr/bin/sh)
Program sh found: YES (/usr/bin/sh)
Program sh found: YES (/usr/bin/sh)
Program xsltproc found: YES (/usr/bin/xsltproc)
Configuring custom-entities.ent using configuration
Message: Skipping bootctl.1 because ENABLE_EFI is false
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Message: Skipping journal-remote.conf.5 because HAVE_MICROHTTPD is false
Message: Skipping journal-upload.conf.5 because HAVE_MICROHTTPD is false
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Message: Skipping loader.conf.5 because ENABLE_EFI is false
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
Program ln found: YES (/usr/bin/ln)
...
Let's suffer one message only for each command. Hopefully we can silence
even this when https://github.com/mesonbuild/meson/issues/8642 is
resolved.
(cherry picked from commit
596f5101f29c10256208132bfa9c502bf898fd8b)
(cherry picked from commit
271b7dcbadd9fed70f87f29f30ef0925619037c9)
Anita Zhang [Thu, 13 May 2021 08:17:51 +0000 (01:17 -0700)]
run: update checks to allow running with a user's bus
systemd-run is documented to as being able to connect and run on a
specific user bus with "--user --machine=lennart@.host" arguments.
This PR updates some logic that prevented this from working.
(cherry picked from commit
cbdc29492097e24ef3320280bc2a8dedbce02d9a)
(cherry picked from commit
cc589cce9815cabb0bed6d0695ec3ff77beebd06)
(cherry picked from commit
2a1d508107c6d9c37c7867c08b15ccb01d3ee0bd)
Michael Catanzaro [Tue, 11 May 2021 13:24:55 +0000 (08:24 -0500)]
resolved.conf.in: add missing Quad9 servers
The example configuration is missing half of Quad9's addresses.
(cherry picked from commit
aa2b370dddc7e37df33769a488d6c3dce89b4e17)
(cherry picked from commit
4b8d52f4f09fe7f514cc982ad945153565503127)
(cherry picked from commit
ed1d8c83c81502437943f6a6588e56813f6b0b75)
Lennart Poettering [Tue, 11 May 2021 20:21:52 +0000 (22:21 +0200)]
resolved: be more careful with weird links with low MTUs
Apparently CAN links will show up in rtnetlink with very low MTUs. We
shouldn't consider them relevant if no IP is spoken over them, since
these MTUs are irrelevant for us then.
Hence, let's check if there's an address assigned to the link before
considering its MTU.
As additional safety net filter out MTUs smaller than the minimum DNS
packet size, too.
Finally, in case we don't find any suitable interface MTU, let's default
to 1500 as the generic Ethernet MTU.
Fixes: #19396
(cherry picked from commit
5a0d0b8f9cdfcbb82c4a89b28f0ebce414c9ecfe)
(cherry picked from commit
3fd268d20979850a70453ed5f8891a0f03344bf2)
(cherry picked from commit
ad9277d6834b5496004c98c80d5a7856afbd2861)
Lennart Poettering [Mon, 16 Nov 2020 20:00:24 +0000 (21:00 +0100)]
resolved: add udp_header_size() helper
(cherry picked from commit
4565863fff974e69d23a7c5a5237528bc5573a17)
(cherry picked from commit
f3f51965c9f2501de62dc5a99f7f86e2869ce614)
Lennart Poettering [Wed, 12 May 2021 08:33:27 +0000 (10:33 +0200)]
pam: fix typo try_authtok → use_authtok
This was a copy/paste mistae apparently, there's not "try_authtok" and
this was supposed to copy what Fedora uses, which uses "use_authtok"
correctly. Hence adjust this.
Fixes: #19369
(cherry picked from commit
971c07fc6812315c2b27015dfcc652a747f919ed)
(cherry picked from commit
ca276dcddc4def7348e2cb897fbf7a8b26bfc5ed)
(cherry picked from commit
dd4f87a8d138d5307cf00c958da0da70dc542a2c)
zsien [Mon, 10 May 2021 07:42:54 +0000 (15:42 +0800)]
bootctl: same entry path check case-insensitive
Some motherboards convert the path to uppercase under certain circumstances
(e.g. after booting into the Boot Menu in the ASUS ROG STRIX B350-F GAMING).
(cherry picked from commit
5c2e5957678462d871c5c2ea5261becec5f8f80f)
(cherry picked from commit
379679f807072b4d554711bc61b769d72ecc98d6)
(cherry picked from commit
6647cff7766faed5cb57373abc7439b048304638)
Lucas Magasweran [Mon, 10 May 2021 08:11:28 +0000 (10:11 +0200)]
man: network: use `networkctl list` instead of `status` to list network interface type
To determine the network interface type for use in the `Type=` directive, it is more concise to use the `list` command. Whereas, the `status` command requires an interface parameter.
For example, on a RaspberryPi 4 the following shows that the `wlan0` interface type `wlan` is more coveniently listed by the `list` command.
```
root@raspberrypi4-64:~# networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routable configured
3 wlan0 wlan off unmanaged
3 links listed.
```
Whereas the `networkctl status` command doesn't include this information.
```
root@raspberrypi4-64:~# networkctl status
● State: routable
Address: 192.168.1.141 on eth0
fd8b:8779:b7a4::f43 on eth0
fd8b:8779:b7a4:0:dea6:32ff:febe:d1ce on eth0
fe80::dea6:32ff:febe:d1ce on eth0
Gateway: 192.168.1.1 (CZ.NIC, z.s.p.o.) on eth0
DNS: 192.168.1.1
May 07 14:17:18 raspberrypi4-64 systemd-networkd[212]: eth0: Gained carrier
May 07 14:17:19 raspberrypi4-64 systemd-networkd[212]: eth0: Gained IPv6LL
May 07 14:17:19 raspberrypi4-64 systemd-networkd[212]: eth0: DHCPv6 address fd8b:8779:b7a4::f43/128 timeout preferred -1 valid -1
May 07 14:17:21 raspberrypi4-64 systemd-networkd[212]: eth0: DHCPv4 address 192.168.1.141/24 via 192.168.1.1
```
To get the interface type using the `status` command you need to specify an additional argument.
```
root@raspberrypi4-64:~# networkctl status wlan0
● 3: wlan0
Link File: /lib/systemd/network/99-default.link
Network File: n/a
Type: wlan
State: off (unmanaged)
Path: platform-
fe300000.mmcnr
Driver: brcmfmac
HW Address: dc:a6:32:be:d1:cf (Raspberry Pi Trading Ltd)
MTU: 1500 (min: 68, max: 1500)
QDisc: noop
IPv6 Address Generation Mode: eui64
Queue Length (Tx/Rx): 1/1
```
(cherry picked from commit
2480ca95bac0f1bed350ba8d5aef1ef92be0f8a4)
(cherry picked from commit
56ba53b17338f37c211a1c1ee0686ff4e5c09d28)
(cherry picked from commit
45df8bbcacbdea03d9f2c2d9c28e8b774b170578)
Lucas Magasweran [Mon, 10 May 2021 08:09:56 +0000 (10:09 +0200)]
network: examples: use wlan for Type instead of wifi
(cherry picked from commit
b419e8776bc2dc1ca113c8332ed465724bff053a)
(cherry picked from commit
bf3d671b379cc683375d62f109f133c1703dd828)
(cherry picked from commit
fcb48553e1bf9dab872dc5796f2501f947f8953b)
Roman Beranek [Fri, 30 Apr 2021 13:51:44 +0000 (15:51 +0200)]
resolve: remove RRs from zones before an update
During an update of RRs, the records of each DNS-SD service are
replaced with new ones. However the old RRs can only be removed from
the mDNS scopes as long as they remain accessible from the DnssdService
structures, otherwise they remain stuck there.
Therefore the removal must take place before the update.
(cherry picked from commit
ee3713b71ddf182852a399953968a2b39af22104)
(cherry picked from commit
46ee05ed1fca9c5637ec5cfbb4f71c84f94b3db6)
(cherry picked from commit
8082864ebba8f2ce1e6afb08cac15daeed4dca3d)
Lennart Poettering [Wed, 5 May 2021 16:57:30 +0000 (18:57 +0200)]
nss-systemd: properly handle empty membership lists
When we are queried for membership lists on a system that has exactly
zero, then we'll return ESRCH immediately instead of at EOF. Which is
OK, but we need to handle this in various places, and not get confused
by it.
(cherry picked from commit
a1aa41e4e175c2712b97600d7e10e9d6c58e5543)
(cherry picked from commit
d0f8a01a74e5a1bed4d687339abde774cb944579)
(cherry picked from commit
83c39430c06620ab208cdeeaaef9da31dd882a91)
Lennart Poettering [Wed, 5 May 2021 14:05:43 +0000 (16:05 +0200)]
nss-systemd: reset the right field
(cherry picked from commit
1fdfca4da739f47516513afc66d4c7008c9badfd)
(cherry picked from commit
18babc7b290de4c0108b2fe39400c3e9c471ef67)
(cherry picked from commit
c3dfbd10da31324158363d6da50345ece24ccaf5)
Franck Bui [Tue, 27 Apr 2021 08:59:24 +0000 (10:59 +0200)]
system-conf: drop reference to ShutdownWatchdogUsec=
Commit
65224c1d0e50667a87c2c4f840c49d4918718f80 renamed ShutdownWatchdogUsec
into RebootWatchdogUsec but left a reference of ShutdownWatchdogUsec in
system.conf.
(cherry picked from commit
45b1fc3a88b2f5102ecabfabdf0ee4f175aecd64)
(cherry picked from commit
54b5a1b21b69d674e55b69be79ef86e5b2215406)
(cherry picked from commit
d582e0ca0bd8408449ec5408e7a4a644404fae30)
Zbigniew Jędrzejewski-Szmek [Fri, 23 Apr 2021 10:40:07 +0000 (12:40 +0200)]
core/service: also reject deserialized commands with no argv[0]
I'm pretty sure that bad things would happen later on.
(cherry picked from commit
90204792461030dbc8645d8511e7ac8d1b4f1ca2)
(cherry picked from commit
d113fd4e0756b1b6f5543a47d0943af4564293ff)
(cherry picked from commit
6c177c530027262aa87cfb026dd5537859d2ff8e)
Zbigniew Jędrzejewski-Szmek [Fri, 23 Apr 2021 10:39:03 +0000 (12:39 +0200)]
core/service: fix deserialization of non-absolute commands
We'd fail with:
Apr 23 10:58:26 systemd[1]: Deserializing state...
Apr 23 10:58:26 systemd[1]: testsuite-01.service: Failed to parse serialized command "ExecStart 0 sh "sh" "-e" "-x" "-c" "systemctl --state=failed --no-legend --no-pager >/failed ; systemctl daemon-reload ; echo OK >/testok"": Invalid argument
Apr 23 10:58:26 systemd[1]: testsuite-01.service: Reinstalled deserialized job testsuite-01.service/start as 209
This was missed in
5008da1ec1, and apparently nobody noticed until now :(
(cherry picked from commit
1a128a468ddd1070651478c36eae76e31f580b67)
(cherry picked from commit
27606d5448dcaef17d256ced7e89b963a13cfec4)
(cherry picked from commit
3b7a2cf026b6c810dde54683561dbc5ee31c59c1)
Yu Watanabe [Mon, 26 Apr 2021 00:03:33 +0000 (09:03 +0900)]
network: update comment and log message
After
4b30f2e135ee84041bb597edca7225858f4ef4fb, reading stable_secret
sysctl property fails with -ENOMEM, instead of -EIO.
This is due to read_full_virtual_file() uses read() as the backend while
read_one_line_file() uses fgetc(). And each functions return different
error on fails.
Anyway, the failure is harmless here. So, the log message and comment is
updated.
Closes one of the issues in #19410.
(cherry picked from commit
0e27527170aa0179f2a4b3b55b78ddc049f815b9)
(cherry picked from commit
2417e9b59aa654e4b3def3399576ebbc2cdd7c95)
(cherry picked from commit
0d80d62a87862f46f62c6c17ad6d682ad6228049)
Yangyang Shen [Wed, 24 Mar 2021 13:23:01 +0000 (21:23 +0800)]
journald: enforce longer line length limit during "setup" phase of stream protocol
This PR made modification on Lennart Poettering's basis. Fix the LineMax's function failure problem.
Signed-off-by: Yangyang Shen <shenyangyang4@huawei.com>
(cherry picked from commit
80e9720616df0eeaba75874fd86fbfbe8b7a03a7)
(cherry picked from commit
9d5c5e4fab6e4816babbd4b74787b43fa5e4440a)
(cherry picked from commit
655ba5aade32e49a73596fcfb2bbd1e787bce235)
Lennart Poettering [Tue, 20 Apr 2021 13:56:03 +0000 (15:56 +0200)]
sd-device: use right clock when comparing initialization usec
we actually use CLOCK_MONOTONIC for the timestamp, hence when
comparing/subtracting it from the current time, also use
CLOCK_MONOTONIC.
(cherry picked from commit
02ef01ade3b16c05dfc8698181d7f562f4934ef3)
(cherry picked from commit
873ad71291e942054dd96ca1a9000cc98f21487a)
(cherry picked from commit
4cf613b3f92ed541ff289c037febbeb80d5742b9)
Lennart Poettering [Tue, 20 Apr 2021 15:06:21 +0000 (17:06 +0200)]
sd-device: use right type for usec_initialized
(cherry picked from commit
a156eb89c827206ee5b51d53016ba63be0c90449)
(cherry picked from commit
d6b0efcdd83a937363267ed751fd9a1085505394)
(cherry picked from commit
434d22b7c6ebb0c2f9eb33afa28cb4d2f744adea)
Yu Watanabe [Tue, 20 Apr 2021 00:23:33 +0000 (09:23 +0900)]
wifi-util: do not set zero errno to log_debug_errno()
(cherry picked from commit
66205cb3f597e43c8446d122fa4cc849c4f101d7)
(cherry picked from commit
8eaf2da0f6c9fbea42d44343c30361dcf79702bf)
(cherry picked from commit
e3640b026a7b26931d7760b0cec5fb51f65797bf)
Peter Hutterer [Tue, 20 Apr 2021 07:09:48 +0000 (17:09 +1000)]
shell-completion: use base.lst, not xorg.lst
Since 2005 xorg.lst has been the legacy symlink to the real file base.lst.
(cherry picked from commit
7a4afd3a15f201a2230dce1f640fc37d18bc39ac)
(cherry picked from commit
6b5621353981ee36280e6c4f08540fc24c19ca26)
(cherry picked from commit
f66253f0e3bca4bb5e3a4ce9a54c3f1de7d3e886)
Jason Francis [Mon, 19 Apr 2021 16:16:26 +0000 (12:16 -0400)]
sd-login: fix wrong constructor used in sd_login_monitor manpage example
(cherry picked from commit
941c5275eaaf8d22915eb876045d2173bdbb7d4c)
(cherry picked from commit
17cb088d6dd3ac940a299c6c7201085252f1367d)
(cherry picked from commit
b52a4350de4931603ab45234614fe1fe17ebdf6a)
Jason Francis [Mon, 19 Apr 2021 16:13:03 +0000 (12:13 -0400)]
sd-login: correct prototype of sd_peer_get_cgroup
(cherry picked from commit
a8310e39e996b9b5f63d897879aecf8988261bdb)
(cherry picked from commit
fa7f835f79d4da8ee6d7403be43a0ba4d24b9fb2)
(cherry picked from commit
60d3eeef5e803997e1c9356d543d460a61f1b4dc)
Zbigniew Jędrzejewski-Szmek [Wed, 14 Apr 2021 20:06:02 +0000 (22:06 +0200)]
Zbigniew Jędrzejewski-Szmek [Wed, 14 Apr 2021 15:10:36 +0000 (17:10 +0200)]
shared/module-util: fix errno value passed to log function
If r == 0, no harm done. But if r > 0, this would be interpreted as an
errno value, wrongly.
(cherry picked from commit
a2eb2267e44580446ecad37e7206e729cfd78155)
(cherry picked from commit
e70a773f85ceb64435de3d47c12b07c08605f591)
(cherry picked from commit
c6d3623e9e53cc4c1b3e05fa665d2c8791212b74)
Zbigniew Jędrzejewski-Szmek [Wed, 14 Apr 2021 10:14:01 +0000 (06:14 -0400)]
partition, random-seed, logind: fix log messages with %m
We would print "...: Success", which is not too terrible, but not pretty
either.
(cherry picked from commit
111a3aae71fa019710216cc5b7aa95b7c8db0937)
(cherry picked from commit
c032a26df67903e0c65150b5cc68ade35aa47c03)
(cherry picked from commit
7b535fcda495ca8a73133526484340925d754bf6)
Zbigniew Jędrzejewski-Szmek [Wed, 14 Apr 2021 09:54:17 +0000 (05:54 -0400)]
sd-device: improve log message and tweak style
We shouldn't say the attribute is missing right after ruling out ENOENT.
(cherry picked from commit
aca591ac55e5ee364905aec975388c5e30d0476c)
(cherry picked from commit
e31914aa17df889ae10f0964a8bbc8c00e0f045b)
(cherry picked from commit
645c85022ac6c035ccdd0590db687c5be1147e85)
Luca Boccassi [Wed, 14 Apr 2021 20:26:50 +0000 (21:26 +0100)]
test: use systemd-run --wait in TEST-44-LOG-NAMESPACE
The test appears to be occasionally failing. It uses systemd-run to echo
'hello world' into a namespaced journal and then uses journalctl to look for it,
but it doesn't wait.
In the failed runs it can't find it, but the automated journal dump shows
the message at the end.
Use --wait to avoid races.
(cherry picked from commit
cf9844ffabd7fd51f22e729692b79d55cd7bdd76)
(cherry picked from commit
2c17e13ae48b94a0fd02c7746d723b26a0f3dc65)
(cherry picked from commit
bed66a8d19566adf94386482fe5ee0216b66f848)
Zbigniew Jędrzejewski-Szmek [Wed, 14 Apr 2021 08:55:09 +0000 (04:55 -0400)]
libsystemd-network: fix dhcp option buffer confusion
We were writing to the wrong buffer with a wrong offset :(
Bug present since the original introduction of the code in
04b28be1a306fd2ba454d3ee333d63df71aa3873.
(cherry picked from commit
828b603a791edd04a5c3603456aa8caca44ce67e)
(cherry picked from commit
cd1fc467f72e607bcd2464651b68f31bd2a8791a)
(cherry picked from commit
3def84156c37b9a873c29bb93afe5ddaa341c698)
Sevan Janiyan [Wed, 14 Apr 2021 23:01:53 +0000 (00:01 +0100)]
Yu Watanabe [Sun, 11 Apr 2021 12:25:16 +0000 (21:25 +0900)]
network: add missing default setting in networkd.conf
(cherry picked from commit
6bfadad9bb6eaf614da92eba0a9b6243e8645018)
(cherry picked from commit
ee24f9346630b6d59e88ef0989f943444e752569)
(cherry picked from commit
5d91d5a61a88d4b5a2b92d5f665a5dd5dd99d6bd)
gaoyi [Tue, 13 Apr 2021 10:59:46 +0000 (18:59 +0800)]
udev: delete useless codes
It seems no one will touch queue.bin
(cherry picked from commit
993eb00016a75cf085eed85cf626a6995e96ab3d)
(cherry picked from commit
a511010f380397e8bb08816288e31b1666dc11b9)
(cherry picked from commit
74ae332b68785b878b25facac43d166d1c85e575)
Francois Gervais [Mon, 12 Apr 2021 22:25:29 +0000 (18:25 -0400)]
load-fragment: parse specifiers in CPUAffinity= (#19281)
(cherry picked from commit
54cfe9a75f0e84d0604d39b87b1d919542336809)
(cherry picked from commit
bf3bd598136397b5371188bcdec0127e56a1db9a)
(cherry picked from commit
595b1cefbb71397ba08b770136e461022d774d1f)
Zbigniew Jędrzejewski-Szmek [Mon, 12 Apr 2021 12:03:32 +0000 (14:03 +0200)]
meson: do not fail if rsync is not installed with meson 0.57.2
https://github.com/mesonbuild/meson/issues/8641
Our CI started to fail. Even if the change is reverted in meson,
we need a quick workaround here.
(cherry picked from commit
7c5fd25119a495009ea62f79e5daec34cc464628)
(cherry picked from commit
f6435a07c1ca4b895573eba4a64dcf4bef3fb92b)
(cherry picked from commit
f4a1812f95d0c215ef3a9fec24e055bc976c41f1)