mirror of
https://github.com/systemd/systemd.git
synced 2025-01-09 01:18:19 +03:00
test: skip TEST-84-STORAGETM if running with bugged libnvme
libnvme 1.11 appears to require a kernel built with NVME TLS
kconfigs, and fails hard if it is not, as the expected
privileged keyring '.nvme' is not present. We cannot just
create it from userspace, as privileged keyrings can only
be created by the kernel itself (those starting with '.').
Skip the test if the library exactly matches this version.
https://github.com/linux-nvme/nvme-cli/issues/2573
Fixes https://github.com/systemd/systemd/issues/35130
(cherry picked from commit 893aa45886
)
This commit is contained in:
parent
04ee5e25a1
commit
d8ec2770b7
@ -3,6 +3,14 @@
|
||||
set -eux
|
||||
set -o pipefail
|
||||
|
||||
if systemd-analyze compare-versions "$(nvme --version | grep libnvme | awk '{print $3}')" eq 1.11; then
|
||||
if grep -q "CONFIG_NVME_TCP_TLS is not set" "/boot/config-$(uname -r)" 2>/dev/null || grep -q "CONFIG_NVME_TCP_TLS is not set" "/usr/lib/modules/$(uname -r)/config" 2>/dev/null; then
|
||||
# See: https://github.com/linux-nvme/nvme-cli/issues/2573
|
||||
echo "nvme-cli is broken and requires TLS support in the kernel" >/skipped
|
||||
exit 77
|
||||
fi
|
||||
fi
|
||||
|
||||
modprobe -v nvmet-tcp
|
||||
modprobe -v nvme-tcp
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user