From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "david@fromorbit.com" <david@fromorbit.com>,
"djwong@kernel.org" <djwong@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: [PATCH v2 1/6] idmapped-mount: split setgid test from test-core
Date: Fri, 8 Apr 2022 10:17:34 +0000 [thread overview]
Message-ID: <625019FD.2030606@fujitsu.com> (raw)
In-Reply-To: <624F9C07.80808@fujitsu.com>
on 2022/4/8 9:20, xuyang2018.jy@fujitsu.com wrote:
> on 2022/4/7 20:55, Christian Brauner wrote:
>> On Thu, Apr 07, 2022 at 08:09:30PM +0800, Yang Xu wrote:
>>> Since we plan to increase setgid test covertage, it will find new bug
>>> , so add a new test group test-setgid is better.
>>>
>>> Also add a new test case to test test-setgid instead of miss it.
>>>
>>> Signed-off-by: Yang Xu<xuyang2018.jy@fujitsu.com>
>>> ---
>>> src/idmapped-mounts/idmapped-mounts.c | 19 +++++++++++++++----
>>> tests/generic/999 | 26 ++++++++++++++++++++++++++
>>> tests/generic/999.out | 2 ++
>>
>> I actually didn't mean to split out the existing setgid tests. I mean
>> adding new ones for the test-cases you're adding. But how you did it
>> works for me too and is a bit nicer. I don't have a strong opinion so as
>> long as Dave and Darrick are fine with it then this seems good to me.
> Ok, let's listen ..
When I write v3, I add mknodat patch as 1st patch and tmpfile as 2nd
patch(by using a file doesn't under DIR1 directory, so I don't need to
concern about xfs_irix_sgid_inherit_enabled), errno reset to 0 as 3st
patch. It seems this way can't introduce the new failure for generic/633.
So I will add a new group for umask and acl and add new case for them
instead of split setgid case from test-core group.
ps: I doubt whether I need to send two patch sets(one is about
mknodat,tmpfile,errno, the another is about umask,acl,new case).
What do you think about this?
Best Regards
Yang Xu
>>
>> One note about the test name/numbering though. It seems you haven't
>> added the test using the provided xfstest infrastructure to do that.
>> Instead of manually adding the test you should run the "new" script.
>>
>> You should run:
>>
>> ~/src/git/xfstests$ ./new generic
>>
>> Next test id is 678
>> Append a name to the ID? Test name will be 678-$name. y,[n]:
>> Creating test file '678'
>> Add to group(s) [auto] (separate by space, ? for list): auto quick attr idmapped mount perms
>> Creating skeletal script for you to edit ...
>>
>> that'll automatically figure out the correct test number etc.
> Thanks, TBH, I don't know this usage. I don't name to 678 because
> fstests patchwork has others new case(in reviewing), so I add a biger
> number.
>
> Best Regards
> Yang Xu
next prev parent reply other threads:[~2022-04-08 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 12:09 [PATCH v2 1/6] idmapped-mount: split setgid test from test-core Yang Xu
2022-04-07 12:09 ` [PATCH v2 2/6] idmapped-mounts: Add mknodat operation in setgid test Yang Xu
2022-04-07 13:40 ` Christian Brauner
2022-04-08 3:02 ` xuyang2018.jy
2022-04-07 12:09 ` [PATCH v2 3/6] idmapped-mounts: Reset errno to zero after detect fs_allow_idmap Yang Xu
2022-04-07 12:59 ` Christian Brauner
2022-04-07 12:09 ` [PATCH v2 4/6] idmapped-mounts: Add umask(S_IXGRP) wrapper for setgid_create* cases Yang Xu
2022-04-07 15:12 ` Christian Brauner
2022-04-08 3:38 ` xuyang2018.jy
2022-04-07 12:09 ` [PATCH v2 5/6] idmapped-mounts: Add setfacl(S_IXGRP) " Yang Xu
2022-04-07 12:09 ` [PATCH v2 6/6] idmapped-mounts: Add open with O_TMPFILE operation in setgid test Yang Xu
2022-04-07 13:43 ` Christian Brauner
2022-04-08 3:58 ` xuyang2018.jy
2022-04-08 7:34 ` Zorro Lang
2022-04-08 7:55 ` xuyang2018.jy
2022-04-07 12:55 ` [PATCH v2 1/6] idmapped-mount: split setgid test from test-core Christian Brauner
2022-04-08 1:20 ` xuyang2018.jy
2022-04-08 10:17 ` xuyang2018.jy [this message]
2022-04-08 10:33 ` Christian Brauner
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=625019FD.2030606@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).