From: Matthew Wilcox <willy@infradead.org>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
viro@zeniv.linux.org.uk, david@fromorbit.com, djwong@kernel.org,
brauner@kernel.org, jlayton@kernel.org
Subject: Re: [PATCH v6 1/4] fs: move sgid strip operation from inode_init_owner into inode_sgid_strip
Date: Mon, 25 Apr 2022 03:45:41 +0100 [thread overview]
Message-ID: <YmYLVfZC3h8l7XY1@casper.infradead.org> (raw)
In-Reply-To: <1650856181-21350-1-git-send-email-xuyang2018.jy@fujitsu.com>
On Mon, Apr 25, 2022 at 11:09:38AM +0800, Yang Xu wrote:
> This has no functional change. Just create and export inode_sgid_strip
> api for the subsequent patch. This function is used to strip inode's
> S_ISGID mode when init a new inode.
Why would you call this inode_sgid_strip() instead of
inode_strip_sgid()?
next prev parent reply other threads:[~2022-04-25 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 3:09 [PATCH v6 1/4] fs: move sgid strip operation from inode_init_owner into inode_sgid_strip Yang Xu
2022-04-25 2:45 ` Matthew Wilcox [this message]
2022-04-25 3:08 ` xuyang2018.jy
2022-04-25 11:29 ` Christian Brauner
2022-04-25 17:33 ` Matthew Wilcox
2022-04-26 1:22 ` xuyang2018.jy
2022-04-25 3:09 ` [PATCH v6 2/4] fs: Add missing umask strip in vfs_tmpfile Yang Xu
2022-04-25 16:54 ` Darrick J. Wong
2022-04-25 3:09 ` [PATCH v6 3/4] fs: strip file's S_ISGID mode on vfs instead of on underlying filesystem Yang Xu
2022-04-25 16:51 ` Darrick J. Wong
2022-04-26 1:25 ` xuyang2018.jy
2022-04-25 3:09 ` [PATCH v6 4/4] ceph: Remove S_ISGID stripping code in ceph_finish_async_create Yang Xu
2022-04-25 16:53 ` [PATCH v6 1/4] fs: move sgid strip operation from inode_init_owner into inode_sgid_strip Darrick J. Wong
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=YmYLVfZC3h8l7XY1@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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 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.