From: Petr Vorel <pvorel@suse.cz>
To: Christian Brauner <brauner@kernel.org>
Cc: Martin Doucha <martin.doucha@suse.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [LTP] [RFC PATCH 1/1] creat09: Fix on more restrictive umask
Date: Mon, 11 Jul 2022 07:25:50 +0200 [thread overview]
Message-ID: <Ysu0XlNGy2F+uInC@pevik> (raw)
In-Reply-To: <20220708143728.r655waixwr3x7xtg@wittgenstein>
> On Thu, Jul 07, 2022 at 08:04:18PM +0200, Petr Vorel wrote:
> > Hi Xu,
> > > Hi Petr
> > > Share some process with you...
> > > I have rejected this patch and a kernel patchset[1] is plan to fix this
> > > but doesn't merged to upstream kernel due to none continue to review
> > > this(It is about one month since v9...)
> > > TBH, this case only tests simple creat file with open but miss
> > > open with O_TMPFILE[2]
> > > mknodat[3]
> > > setgid strip logic is not only affected by umask but also include acl
> > > operations[4].
> > Thanks a lot for an update.
> > Al, Christian, Amir, could you please have look on v9?
> Afaict, I reviewed v9 and left comments and had pointed out things that
> needed to be changed. So I'd wait for v10 (I'm on vacation next week
> though.).
Thanks a lot, sorry for overlooking your change requests!
Kind regards,
Petr
> Christian
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-07-11 5:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:12 [LTP] [RFC PATCH 1/1] creat09: Fix on more restrictive umask Petr Vorel
2022-03-18 7:59 ` xuyang2018.jy
2022-03-18 10:37 ` xuyang2018.jy
2022-03-18 22:12 ` Darrick J. Wong
2022-03-22 6:28 ` xuyang2018.jy
2022-07-06 9:37 ` xuyang2018.jy
2022-07-07 18:04 ` Petr Vorel
2022-07-08 14:37 ` Christian Brauner
2022-07-11 3:56 ` xuyang2018.jy
2022-07-11 5:25 ` Petr Vorel [this message]
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=Ysu0XlNGy2F+uInC@pevik \
--to=pvorel@suse.cz \
--cc=brauner@kernel.org \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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