From: Cyril Hrubis <chrubis@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "brauner@kernel.org" <brauner@kernel.org>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4 1/3] syscalls/creat09: Add umask test condition
Date: Wed, 21 Sep 2022 15:55:56 +0200 [thread overview]
Message-ID: <YysX7FVAHO6HkLLZ@yuki> (raw)
In-Reply-To: <12eff5a1-bf6b-59bf-bfca-7a1d4f3ca009@fujitsu.com>
Hi!
> > Yes. Please apply it with fix the messages. Thanks.
>
> I guess you miss this patchset. so ping again.
Sorry for the delay.
I just did quick test and I got failures on XFS on kernel 5.19, wasn't
this supposed to be fixed in 5.19?
...
creat09.c:106: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group
creat09.c:112: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set
creat09.c:106: TPASS: mntpoint/testdir/open.tmp: Owned by correct group
creat09.c:112: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set
creat09.c:120: TINFO: File created with umask(S_IXGRP)
creat09.c:106: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group
creat09.c:110: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set
creat09.c:106: TPASS: mntpoint/testdir/open.tmp: Owned by correct group
creat09.c:110: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set
...
$ uname -r
5.19.0
$ git describe 1639a49ccdce
v5.19-rc7-3-g1639a49ccdce
Is there any in-flight patch for v6.0 that fixes this for XFS?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-21 13:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 8:12 [LTP] [PATCH v4 1/3] syscalls/creat09: Add umask test condition Yang Xu
2022-09-14 7:49 ` xuyang2018.jy
2022-09-14 8:12 ` [LTP] [PATCH v4 2/3] tst_safe_file_at: Add SAFE_FSTATAT macro Yang Xu
2022-09-14 11:30 ` Cyril Hrubis
2022-09-14 8:12 ` [LTP] [PATCH v4 3/3] syscalls/openat: Add new regression test when using open(O_TMPFILE) under umask Yang Xu
2022-09-22 8:52 ` Cyril Hrubis
2022-09-22 9:06 ` xuyang2018.jy
2022-09-22 9:27 ` Cyril Hrubis
2022-09-22 10:02 ` xuyang2018.jy
2022-09-23 10:27 ` Christian Brauner
2022-09-26 1:55 ` xuyang2018.jy
2022-10-10 6:32 ` xuyang2018.jy
2022-09-14 11:28 ` [LTP] [PATCH v4 1/3] syscalls/creat09: Add umask test condition Cyril Hrubis
2022-09-15 0:37 ` xuyang2018.jy
2022-09-20 1:08 ` xuyang2018.jy
2022-09-21 13:55 ` Cyril Hrubis [this message]
2022-09-21 15:40 ` Christian Brauner
2022-09-22 8:00 ` Cyril Hrubis
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=YysX7FVAHO6HkLLZ@yuki \
--to=chrubis@suse.cz \
--cc=brauner@kernel.org \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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