From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Wang Shilong <wshilong@ddn.com>
Cc: Dave Chinner <david@fromorbit.com>,
Wang Shilong <wangshilong1991@gmail.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-fs@vger.kernel.org" <linux-fs@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Andreas Dilger <adilger@dilger.ca>, Li Xi <lixi@ddn.com>
Subject: Re: 答复: [RFC PATCH] ext4: add link file support for {GET,SET}XATTR ioctl
Date: Thu, 14 Feb 2019 07:54:10 -0800 [thread overview]
Message-ID: <20190214155410.GF32253@magnolia> (raw)
In-Reply-To: <BYAPR19MB2758BDB15262B0333504B70ED4670@BYAPR19MB2758.namprd19.prod.outlook.com>
On Thu, Feb 14, 2019 at 08:14:56AM +0000, Wang Shilong wrote:
> Hi Dave, Darrick,
>
> Thanks for good suggestions!
> As my understanding, we could modify
>
> do_fchownat() to change project ID instead of
> group id if AT_FCHOWN_PROJID(new flags) passed in.
>
> Besides that we also need a new flag AT_FCHOWN_PROJ_INHERIT.
> to set/clear inherit attributes?
That sounds reasonable enough to consider as a formal proposal.
> And for Project Get, we might need extend 'struct attr {'
> to include project id.
Let's add a new STATX_PROJID so that statx() callers can fetch it?
Also manpage updates and fstests cases...
--D
> What do you think?
>
> Thanks,
> Shilong
prev parent reply other threads:[~2019-02-14 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 1:47 [RFC PATCH] ext4: add link file support for {GET,SET}XATTR ioctl Wang Shilong
2019-01-31 3:41 ` Dave Chinner
2019-01-31 17:40 ` Darrick J. Wong
2019-01-31 20:43 ` Dave Chinner
2019-02-14 8:14 ` 答复: " Wang Shilong
2019-02-14 15:54 ` Darrick J. Wong [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=20190214155410.GF32253@magnolia \
--to=darrick.wong@oracle.com \
--cc=adilger@dilger.ca \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lixi@ddn.com \
--cc=wangshilong1991@gmail.com \
--cc=wshilong@ddn.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;
as well as URLs for NNTP newsgroup(s).