From: Wei Gao via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Skip cgroup-related tests if `/sys/fs/cgroup` readonly
Date: Tue, 26 Sep 2023 03:12:00 -0400 [thread overview]
Message-ID: <ZRKEQKHgkpVURMFs@wegao> (raw)
In-Reply-To: <20230925151728.GE60471@pevik>
On Mon, Sep 25, 2023 at 05:17:28PM +0200, Petr Vorel wrote:
> Hi all,
>
> > Otherwise clone303 fails with TBROK when `/sys/fs/cgroup` is mounted as
> > read-only which is normal in a container. The test result should better
> > be TCONF like it is already done in case of a permission error.
>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
Tested-by: Wei Gao <wegao@suse.com>
>
> IMHO another candidate for merging before release.
>
> Kind regards,
> Petr
>
> > Signed-off-by: Marius Kittler <mkittler@suse.de>
> > ---
> > lib/tst_cgroup.c | 3 +++
> > 1 file changed, 3 insertions(+)
>
> > diff --git a/lib/tst_cgroup.c b/lib/tst_cgroup.c
> > index fdeac6059..5240aadaa 100644
> > --- a/lib/tst_cgroup.c
> > +++ b/lib/tst_cgroup.c
> > @@ -383,6 +383,9 @@ static void cgroup_dir_mk(const struct cgroup_dir *const parent,
> > tst_brk(TCONF | TERRNO,
> > "Lack permission to make '%s/%s'; premake it or run as root",
> > dpath, dir_name);
> > + } else if (errno == EROFS) {
> > + tst_brk(TCONF | TERRNO, "'%s/%s' must not be read-only",
> > + dpath, dir_name);
> > } else {
> > tst_brk(TBROK | TERRNO,
> > "mkdirat(%d<%s>, '%s', 0777)",
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-26 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 14:42 [LTP] [PATCH v1] Skip cgroup-related tests if `/sys/fs/cgroup` readonly Marius Kittler
2023-09-25 15:17 ` Petr Vorel
2023-09-26 7:12 ` Wei Gao via ltp [this message]
2023-09-27 5:52 ` Petr Vorel
2023-09-27 7:36 ` Wei Gao via ltp
2023-09-26 10:27 ` Richard Palethorpe
2023-09-27 5:43 ` Petr Vorel
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=ZRKEQKHgkpVURMFs@wegao \
--to=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rpalethorpe@suse.com \
--cc=wegao@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox