2020-03-04 12:35:06 +03:00
#!/usr/bin/env bash
2021-10-17 19:13:06 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
2021-04-09 20:39:41 +03:00
set -eux
2019-03-19 21:54:46 +03:00
set -o pipefail
# Let's run this test only if the "memory.oom.group" cgroupfs attribute
# exists. This test is a bit too strict, since the "memory.events"/"oom_kill"
# logic has been around since a longer time than "memory.oom.group", but it's
# an easier thing to test for, and also: let's not get confused by older
# kernels where the concept was still new.
2019-12-10 11:43:14 +03:00
if test -f /sys/fs/cgroup/system.slice/testsuite-32.service/memory.oom.group; then
2019-03-19 21:54:46 +03:00
systemd-analyze log-level debug
systemd-analyze log-target console
# Run a service that is guaranteed to be the first candidate for OOM killing
2019-12-10 11:43:14 +03:00
systemd-run --unit= oomtest.service \
-p Type = exec -p OOMScoreAdjust = 1000 -p OOMPolicy = stop -p MemoryAccounting = yes \
sleep infinity
2019-03-19 21:54:46 +03:00
# Trigger an OOM killer run
2019-12-10 11:43:14 +03:00
echo 1 >/proc/sys/kernel/sysrq
echo f >/proc/sysrq-trigger
2019-03-19 21:54:46 +03:00
while : ; do
2021-04-09 20:54:42 +03:00
STATE = " $( systemctl show -P ActiveState oomtest.service) "
2019-03-19 21:54:46 +03:00
[ " $STATE " = "failed" ] && break
sleep .5
done
2021-04-09 20:54:42 +03:00
RESULT = " $( systemctl show -P Result oomtest.service) "
2019-03-19 21:54:46 +03:00
test " $RESULT " = "oom-kill"
systemd-analyze log-level info
fi
2019-12-10 11:43:14 +03:00
echo OK >/testok
2019-03-19 21:54:46 +03:00
exit 0