| Message ID | 160382534122.1202316.7161591166906029132.stgit@magnolia (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | xfstests: random fixes | expand |
On Tue, Oct 27, 2020 at 12:02:21PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@oracle.com> > > If systemd is available, run each test in its own temporary systemd > scope. This enables the test harness to forcibly clean up all of the > test's child processes (if it does not do so itself) so that we can move > into the post-test unmount and check cleanly. Can you explain what this mean in more detail? Most importantly what problems it fixes.
On Wed, Oct 28, 2020 at 07:44:07AM +0000, Christoph Hellwig wrote: > On Tue, Oct 27, 2020 at 12:02:21PM -0700, Darrick J. Wong wrote: > > From: Darrick J. Wong <darrick.wong@oracle.com> > > > > If systemd is available, run each test in its own temporary systemd > > scope. This enables the test harness to forcibly clean up all of the > > test's child processes (if it does not do so itself) so that we can move > > into the post-test unmount and check cleanly. > > Can you explain what this mean in more detail? Most importantly what > problems it fixes. I'll answer these in reverse order. :) I frequently run fstests in "low" memory situations (2GB!) to force the kernel to do interesting things. There are a few tests like generic/224 and generic/561 that put processes in the background and occasionally trigger the OOM killer. Most of the time the OOM killer correctly shoots down fsstress or duperemove, but once in a while it's stupid enough to shoot down the test control process (i.e. tests/generic/224) instead. fsstress is still running in the background, and the one process that knew about that is dead. When the control process dies, ./check moves on to the post-test fsck, which fails because fsstress is still running and we can't unmount. After fsck fails, ./check moves on to the next test, which fails because fsstress is /still/ writing to the filesystem and we can't unmount or format. The end result is that that one OOM kill causes cascading test failures, and I have to re-start fstests to see if I get a clean(er) run. This is frustrating in the -rc1 days, where I more frequently observe problems with memory reclaim and OOM kills. (Note: those problems are usually gone by -rc3.) So, the solution I present in this patch is to teach ./check to try to run the test script in a systemd scope. If that succeeds, ./check will tell systemd to kill the scope when the test script exits and returns control to ./check. Concretely, this means that systemd creates a new cgroup, stuffs the processes in that cgroup, and when we kill the scope, systemd kills all the processes in that cgroup and deletes the cgroup. The end result is that fstests now has an easy way to ensure that /all/ child processes of a test are dead before we try to unmount the test and scratch devices. I've designed this to be optional, because not everyone does or wants or likes to run systemd, but it makes QA easier. Hmm, this might make a better commit log. I'll excerpt this into the patch message. --D
[resend; I can't keep track of which messages actually got NOSEND warnings and which ones just dropped off...] On Wed, Oct 28, 2020 at 07:44:07AM +0000, Christoph Hellwig wrote: > On Tue, Oct 27, 2020 at 12:02:21PM -0700, Darrick J. Wong wrote: > > From: Darrick J. Wong <darrick.wong@oracle.com> > > > > If systemd is available, run each test in its own temporary systemd > > scope. This enables the test harness to forcibly clean up all of the > > test's child processes (if it does not do so itself) so that we can move > > into the post-test unmount and check cleanly. > > Can you explain what this mean in more detail? Most importantly what > problems it fixes. I'll answer these in reverse order. :) I frequently run fstests in "low" memory situations (2GB!) to force the kernel to do interesting things. There are a few tests like generic/224 and generic/561 that put processes in the background and occasionally trigger the OOM killer. Most of the time the OOM killer correctly shoots down fsstress or duperemove, but once in a while it's stupid enough to shoot down the test control process (i.e. tests/generic/224) instead. fsstress is still running in the background, and the one process that knew about that is dead. When the control process dies, ./check moves on to the post-test fsck, which fails because fsstress is still running and we can't unmount. After fsck fails, ./check moves on to the next test, which fails because fsstress is /still/ writing to the filesystem and we can't unmount or format. The end result is that that one OOM kill causes cascading test failures, and I have to re-start fstests to see if I get a clean(er) run. This is frustrating in the -rc1 days, where I more frequently observe problems with memory reclaim and OOM kills. (Note: those problems are usually gone by -rc3.) So, the solution I present in this patch is to teach ./check to try to run the test script in a systemd scope. If that succeeds, ./check will tell systemd to kill the scope when the test script exits and returns control to ./check. Concretely, this means that systemd creates a new cgroup, stuffs the processes in that cgroup, and when we kill the scope, systemd kills all the processes in that cgroup and deletes the cgroup. The end result is that fstests now has an easy way to ensure that /all/ child processes of a test are dead before we try to unmount the test and scratch devices. I've designed this to be optional, because not everyone does or wants or likes to run systemd, but it makes QA easier. Hmm, this might make a better commit log. I'll excerpt this into the patch message. --D
On Tue, Oct 27, 2020 at 12:02:21PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@oracle.com> > > If systemd is available, run each test in its own temporary systemd > scope. This enables the test harness to forcibly clean up all of the > test's child processes (if it does not do so itself) so that we can move > into the post-test unmount and check cleanly. > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> > --- > check | 21 ++++++++++++++++++++- > 1 file changed, 20 insertions(+), 1 deletion(-) > > > diff --git a/check b/check > index 5072dd82..47c72fa2 100755 > --- a/check > +++ b/check > @@ -521,6 +521,11 @@ _expunge_test() > return 0 > } > > +# Can we run systemd scopes? > +HAVE_SYSTEMD_SCOPES= > +systemd-run --quiet --unit "fstests-check" --scope bash -c "exit 77" &> /dev/null > +test $? -eq 77 && HAVE_SYSTEMD_SCOPES=yes > + > # Make the check script unattractive to the OOM killer... > OOM_SCORE_ADJ="/proc/self/oom_score_adj" > test -w ${OOM_SCORE_ADJ} && echo -1000 > ${OOM_SCORE_ADJ} > @@ -528,8 +533,22 @@ test -w ${OOM_SCORE_ADJ} && echo -1000 > ${OOM_SCORE_ADJ} > # ...and make the tests themselves somewhat more attractive to it, so that if > # the system runs out of memory it'll be the test that gets killed and not the > # test framework. > +# > +# If systemd is available, run the entire test script in a scope so that we can > +# kill all subprocesses of the test if it fails to clean up after itself. This > +# is essential for ensuring that the post-test unmount succeeds. > _run_seq() { > - bash -c "test -w ${OOM_SCORE_ADJ} && echo 250 > ${OOM_SCORE_ADJ}; exec ./$seq" > + local cmd=(bash -c "test -w ${OOM_SCORE_ADJ} && echo 250 > ${OOM_SCORE_ADJ}; exec ./$seq") > + > + if [ -n "${HAVE_SYSTEMD_SCOPES}" ]; then > + local unit="$(systemd-escape "fs$seq").scope" > + systemd-run --quiet --unit "${unit}" --scope "${cmd[@]}" /me discovers that systemd preserves failed transient scopes (where "failed" means the processes get killed, not that they return nonzero), so this patch has to reset-failed the scope in case the user calls fstests before rebooting. Hence, self NAK. --D > + res=$? > + systemctl stop "${unit}" &> /dev/null > + return "${res}" > + else > + "${cmd[@]}" > + fi > } > > _detect_kmemleak >
diff --git a/check b/check index 5072dd82..47c72fa2 100755 --- a/check +++ b/check @@ -521,6 +521,11 @@ _expunge_test() return 0 } +# Can we run systemd scopes? +HAVE_SYSTEMD_SCOPES= +systemd-run --quiet --unit "fstests-check" --scope bash -c "exit 77" &> /dev/null +test $? -eq 77 && HAVE_SYSTEMD_SCOPES=yes + # Make the check script unattractive to the OOM killer... OOM_SCORE_ADJ="/proc/self/oom_score_adj" test -w ${OOM_SCORE_ADJ} && echo -1000 > ${OOM_SCORE_ADJ} @@ -528,8 +533,22 @@ test -w ${OOM_SCORE_ADJ} && echo -1000 > ${OOM_SCORE_ADJ} # ...and make the tests themselves somewhat more attractive to it, so that if # the system runs out of memory it'll be the test that gets killed and not the # test framework. +# +# If systemd is available, run the entire test script in a scope so that we can +# kill all subprocesses of the test if it fails to clean up after itself. This +# is essential for ensuring that the post-test unmount succeeds. _run_seq() { - bash -c "test -w ${OOM_SCORE_ADJ} && echo 250 > ${OOM_SCORE_ADJ}; exec ./$seq" + local cmd=(bash -c "test -w ${OOM_SCORE_ADJ} && echo 250 > ${OOM_SCORE_ADJ}; exec ./$seq") + + if [ -n "${HAVE_SYSTEMD_SCOPES}" ]; then + local unit="$(systemd-escape "fs$seq").scope" + systemd-run --quiet --unit "${unit}" --scope "${cmd[@]}" + res=$? + systemctl stop "${unit}" &> /dev/null + return "${res}" + else + "${cmd[@]}" + fi } _detect_kmemleak