| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
dissect: add dissection policies
|
| | |
|
| | |
|
|\ \
| | |
| | | |
service: tell service processes that the fdstore is available via an e…
|
| | | |
|
|\ \ \
| |/ /
|/| | |
sd-device: several follow-ups about devlink creation
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Stripping the binaries in the test images makes potential stack straces
quite useless, so let's drop the stripping stuff to make test fails a bit
more developer friendly.
Related: https://github.com/systemd/systemd-centos-ci/pull/616
|
|\ \
| | |
| | | |
os-util: several cleanups and introduce _at() variants of os-release parsers
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To make it consistent with other env vars, e.g. $SYSTEMD_ESP_PATH or
$SYSTEMD_XBOOTLDR_PATH.
This is useful when the root is specified by a file descriptor, instead
of a path.
|
|\ \ \
| |/ /
|/| | |
sd-device,udev: refuse unsafe path in SYMLINK= and TAG=
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All tags are managed under /run/udev/tags, and the directories there are
named with tags. Hence, each tag must be a valid filename.
This also makes all validity check moved to sd-device side, and
makes failure caused by setting invalid tags non-critical.
With this change, an empty string cannot be assigned to TAG=, hence the
test cases are adjusted.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is especially for the case that the path contains "..".
Prompted by https://github.com/systemd/systemd/pull/27164#issuecomment-1498863858.
This also makes SYMLINK= gracefully handle paths prefixed with "/dev/",
and manage devlink paths with path_hash_ops.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
test: a couple of stability tweaks
|
| | | |
| | | |
| | | |
| | | | |
When Ubuntu CI is oversaturated, 60s doesn't seem to be enough.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Without enabling itx, there's no symlink to the org.freedesktop.resolve1
dbus service, so there exists a tiny window in which the sequence of
`systemctl start` and `systemctl service-log-level` commands might fail:
[ 1127.615151] H systemd[1]: Started Network Name Resolution.
[ 1127.617768] H testsuite-75.sh[34]: + systemctl service-log-level systemd-resolved.service debug
[ 1127.621251] H dbus-daemon[54]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.24' (uid=0 pid=119 comm="systemctl service-log-level systemd-resolved>
[ 1127.621336] H systemd[1]: dbus-org.freedesktop.resolve1.service: Failed to load configuration: No such file or directory
[ 1127.621364] H systemd[1]: dbus-org.freedesktop.resolve1.service: Trying to enqueue job dbus-org.freedesktop.resolve1.service/start/replace
[ 1127.621395] H systemd[1]: D-Bus activation failed for dbus-org.freedesktop.resolve1.service: Unit dbus-org.freedesktop.resolve1.service not found.
[ 1127.621965] H dbus-daemon[54]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
[ 1127.622046] H systemd[1]: systemd-resolved.service: D-Bus name org.freedesktop.resolve1 now owned by :1.25
[ 1127.622130] H systemctl[119]: Failed to set log level of org.freedesktop.resolve1 to debug: Unit dbus-org.freedesktop.resolve1.service not found.
Spotted in a couple of recent Ubuntu CI runs.
|
| | |
| | |
| | |
| | | |
For #27187, which should be also caused by #26956.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
My original assumption in 61961e693d was wrong, since we do reset
/dev/console during reexec (see make_console_stdio()), so the test was
quite racy. Let's replace it with something, hopefully, more reliable.
Follow-up to 61961e693d.
|
|\ \
| | |
| | | |
sd-journal: allow to specify compression algorithm through env
|
| | |
| | |
| | |
| | | |
compression algorithm
|
|\ \ \
| | | |
| | | | |
test: introduce TEST-81-GENERATORS
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add some explicit tests for various generators we ship, e.g.:
- systemd-debug-generator
- systemd-environment-d-generator
- systemd-fstab-generator
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A simple test case for issue #27106.
Resolves: #27139
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | | |
The rational is the same as the one described in commit
be0cc2ce6c947aafadb3f42dba405269f670b31c.
|
| |/
|/| |
|
| |
| |
| |
| |
| | |
When invoked by udevadm verify, warn about rules that have PROGRAM
assignments specified after RESULT checks.
|
|\ \
| |/
|/| |
Ensure sysexts do not contain an os-release file, do not load sysexts from /usr[/local]/lib/extensions/
|
| |
| |
| |
| |
| | |
sysexts are not supposed to ship os-release files, enforce this
when loading them
|
|\ \
| | |
| | | |
test: set ReadWritePaths= for test-.services when built w/ coverage
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Let's make the dropin, to make the build dir writable for gcov, a bit
more generic, so it can be used by all units starting with prefix test-.
This should help with a bunch of recent reports about missing coverage I
got, as well as with existing test units using DynamicUser=true.
This might feel a bit like a magic trick from behind the curtains, but I
want to touch the actual tests as little as possible, since it makes them
unnecessarily messy (see the various workarounds for sanitizers), and
the coverage reports are generated only in a specific CI job anyway.
|
| |
| |
| |
| |
| |
| | |
This can be used to prepare an image for firstboot by removing all
files that systemd knows about that contain machine specific
information.
|
| |
| |
| |
| | |
This should fix shellcheck warning SC2004.
|
| |
| |
| |
| | |
Use in-line error handling rather than redirections. Follow up on #27020
|
|/
|
|
|
|
|
|
|
|
|
|
| |
systemd-repart needs to find mkfs.ext4 for the test.
This is located in the directory /usr/sbin on openSUSE Tumbleweed.
But since the variable ALWAYS_SET_PATH in /etc/login.defs is set to yes,
su re-initializes the $PATH variable and removes /usr/sbin.
Hence, mkfs.ext4 is not found and the test fails.
Using setpriv instead of su fixes this issue and is more appropriate to
do the switch user task from root.
[zjs: move setpriv to $BASICTOOLS and force-push to retrigger CI]
|
| |
|
|\
| |
| | |
mkosi: Update to latest
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Drop Netdev= as it was removed in mkosi
- Always install python-psutil in the final image (required for networkd tests)
- Always Install python-pytest in the final image (required for ukify tests)
- Use the narrow glob for all centos python packages
- Drop the networkd mkosi config files (the default image can be used instead)
- Use ".conf" as the mkosi config file suffix everywhere
- Copy src/ to /root/src in the final image and set gdb substitute path in
.gdbinit to make gdb work properly
|
| | |
|
|\ \
| |/
|/| |
systemd-cryptenroll: adding integration test cases
|
| | |
|
| |
| |
| |
| |
| |
| | |
Make sure the ENOENT exception reintroduced by commit
9db7081d83d56cd2523b03f9eb9d67ef1c93c55f is not applied when the parser
is invoked by udevadm verify.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes "sleep" invocations, and makes the notify access testcase a
lot more robust to runtime jitter. We use a pair of fifos in the fs to
sync instead.
Also various other improvoements, including comments.
(Also removes the unnecessary "no-qemu" restriction)
|