From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4, 2/2] cgroup/cgroup_regression_test: Fix umount failure
Date: Wed, 21 Jul 2021 16:37:27 +0200 [thread overview]
Message-ID: <YPgxJwx795fhXgLa@pevik> (raw)
In-Reply-To: <20210719092239.GA1475@atcfdc88>
Hi Leo,
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> rmdir cgroup/0 cgroup/1
> - umount cgroup/
> + tst_umount cgroup/ # Avoid possible EBUSY error
> }
> #---------------------------------------------------------------------------
> @@ -193,7 +193,7 @@ test3()
> wait $pid2 2>/dev/null
> rmdir $cpu_subsys_path/0 2> /dev/null
> - umount cgroup/ 2> /dev/null
> + tst_umount cgroup/ 2> /dev/null # Avoid possible EBUSY error
I'd prefer: # keep "/" to avoid possible EBUSY error
But that can be changed before merge.
More I'm interested if other maintainers agree with me about this approach.
(keep / here instead of in tst_umount())
> check_kernel_bug
> }
> @@ -222,7 +222,7 @@ test4()
> mount -t cgroup -o none,name=foo cgroup cgroup/
> mkdir cgroup/0
> rmdir cgroup/0
> - umount cgroup/
> + tst_umount cgroup/ # Avoid possible EBUSY error
> if dmesg | grep -q "MAX_LOCKDEP_SUBCLASSES too low"; then
> tst_res TFAIL "lockdep BUG was found"
> @@ -254,7 +254,7 @@ test5()
> mount -t cgroup none cgroup 2> /dev/null
> mkdir cgroup/0
> rmdir cgroup/0
> - umount cgroup/ 2> /dev/null
> + tst_umount cgroup/ 2> /dev/null # Avoid possible EBUSY error
I'd drop stderr redirection here. It was here originally, but I suppose it's not
needed when using tst_umount. But that can be done during merge.
...
Kind regards,
Petr
next prev parent reply other threads:[~2021-07-21 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 9:22 [LTP] [PATCH v4, 2/2] cgroup/cgroup_regression_test: Fix umount failure Leo Liang
2021-07-21 14:37 ` Petr Vorel [this message]
2021-07-22 4:35 ` Joerg Vehlow
2021-07-22 6:32 ` Leo Liang
2021-07-22 6:37 ` Joerg Vehlow
2021-07-27 5:27 ` Leo Liang
2021-07-27 13:09 ` Cyril Hrubis
2021-07-27 13:53 ` Petr Vorel
2021-07-29 7:41 ` Leo Liang
2021-07-22 4:55 ` Leo Liang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YPgxJwx795fhXgLa@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.