| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
machinectl: add verb edit and cat to operate on .nspawn files
|
| | |
|
| |
| |
| |
| |
| |
| | |
Make sure /etc/udev/hwdb.d/ exists before creating a file inside it.
Fixes: 95cf8cae77f7 ("test: add coverage test for udevadm")
|
|/
|
|
|
|
|
|
| |
Log an error when a rule line contains conflicting match expressions, e.g.
NAME=="value", NAME!="value"
Log a warning when a rule line contains duplicate expressions, e.g.
NAME=="value", NAME=="value"
|
|\
| |
| | |
Fixes for test 58 repart
|
| |
| |
| |
| |
| |
| | |
Let image_install figures the binary paths out itself as not all distributions
ship the mkfs.* tools in the same location. For example openSUSE ships
mksquashfs in /usr/bin/.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ProtectControlGroups=yes
The interface requires services to write to the cgroup file to activate notifications,
but with ProtectControlGroups=yes we make it read-only. Add a writable bind mount.
Follow-up for 6bb0084204bd93122c9f04391b80aea5a8a0ff08
|
| |
| |
| |
| |
| |
| |
| | |
directory
This avoids hard coding the path of the directory where the unit tests are
installed.
|
|\ \
| | |
| | | |
test-execute: add tests for NetworkNamespacePath=
|
| | |
| | |
| | |
| | | |
Prompted by https://github.com/systemd/systemd/issues/26422#issuecomment-1435772839.
|
| | |
| | |
| | |
| | |
| | | |
If an exotic network driver is loaded, there may exist an unexpected
network interface.
|
| | | |
|
|\ \ \
| | | |
| | | | |
test: add a couple of tests for systemd-path
|
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Maybe, better to check the runtime scope each verb for better log
message, but this is a good start point to not trigger assertion.
Fixes oss-fuzz#56915 (https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56915).
Fixes #26402 and #26754.
|
|\ \ \
| | | |
| | | | |
boot: Drop gnu-efi / Add elf2efi.py
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This drops all mentions of gnu-efi and its manual build machinery. A
future commit will bring bootloader builds back. A new bootloader meson
option is now used to control whether to build sd-boot and its userspace
tooling.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a rules contains several LABEL tokens, the parser used to silently
discard all of them besides the last one without any diagnostics at all.
It's time to break the vow of silence and let the parser issue a warning.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When udevadm verify is invoked without positional arguments, that is,
when no udev rules files are specified, load all rules files from the system
like the udev daemon does, and verify them.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Make sure the test would not collide with anything else by moving
all files it created into a temporary directory.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Use certainly invalid user/group names in the tests that check
unknown user/group diagnostics.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
On Debian the test fails because /run is noexec. Simply create the
script in /tmp (and use a BindPath=), as other tests are doing.
Follow-up for 3b7101183cac4b35a8bd6ea2c1de9260c33f977f
|
|\ \ \
| | | |
| | | | |
udev: add /dev/loop/by-inode/… + /dev/loop/by-ref/… loopback block device symlinks
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
symlinks
Let's test that everything we just added works in combination.
|
|\ \ \
| | | |
| | | | |
Assorted test tweaks
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Necessary for some CI setups where we boot an nspawn container on a host
with older systemd with legacy hierarchy, so systemd mounts its stuff
under /sys/fs/cgroup/systemd.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
mkfs.btrfs (unlike mkfs.ext4) checks if the target already contains
a file system and refuses to continue if so. This causes spurious fails
in case the random garbage on the temporary device matches a valid FS
header:
[ 19.723806] testsuite-64.sh[355]: + udevadm lock --device=/dev/mapper/encbtrfs0 --device=/dev/mapper/encbtrfs1 --device=/dev/mapper/encbtrfs2 --device=/dev/mapper/encbtrfs3 mkfs.btrfs -M -d raid1 -m raid1 -L btrfs_mencdisk -U deadbeef-dead-dead-beef-000000000003 /dev/mapper/encbtrfs0 /dev/mapper/encbtrfs1 /dev/mapper/encbtrfs2 /dev/mapper/encbtrfs3
[ 19.918934] testsuite-64.sh[2494]: ERROR: /dev/mapper/encbtrfs0 appears to contain an existing filesystem (hfsplus)
[ 19.920490] testsuite-64.sh[2494]: ERROR: use the -f option to force overwrite of /dev/mapper/encbtrfs0
Let's force mkfs.btrfs to overwrite the file system in such case.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Let's make the cleanup 'best effort' operation, as sometimes we might
not be able to remove the scsi_debug module, and we don't really care
if it stays loaded:
[ 88.521333] testsuite-17.sh[1827]: ID_TEST=test
[ 88.522015] testsuite-17.sh[1679]: + rmmod scsi_debug
[ 88.524795] testsuite-17.sh[1828]: rmmod: ERROR: Module scsi_debug is in use
[ 88.527786] testsuite-17.sh[1679]: + cleanup_17_10
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Let's attempt to reduce the amount of flakes further when the AWS region
we run in is under heavy load and the hypervisor stars stealing our CPU
time.
Follow-up to e0cbb73911 and c78d18215b.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As the test runs during machine bootup where jobs run in parallel,
busctl might attempt to introspect a job that already finished and fail.
Since in this case we're more interested in crashes/leaks, let's ignore
the exit code.
Follow-up to 16600a8661.
|
|\ \ \
| | | |
| | | | |
Mempressure follow ups
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Follow-up for #26393.
Addresses https://github.com/systemd/systemd/pull/26393#issuecomment-1458655798.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes the PSI window duration we default to for watching memory
pressure events from 1s to 2s. This is because apparently the kernel
will soon disallow window durations other than 2s for unprivileged
processes.
Hence, we'll bump the threshold from 100m to 200ms, and the window from
1s to 2s.
|
|\ \
| | |
| | |
| | |
| | | |
lilyinstarlight/fix/fstab-generator-sysroot-without-cmdline
fstab-generator: use correct targets when /sysroot is specificied in fstab only
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When udev rules file ends with a line continuation, the parser
used to silently ignore the line without any diagnostics at all.
It's time to break the vow of silence and let the parser issue some
error diagnostics.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
test: generate debugging logs for udevd after restart
|
| | |
| | |
| | |
| | |
| | | |
Otherwise, udevd may be busy and udevadm may not receive the reply
for the control packet within the time limit.
|
| | | |
|