From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: cgxu519 <cgxu519@gmx.com>
Cc: shaggy@kernel.org, jfs-discussion@lists.sourceforge.net,
martin@omnibond.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, adilger.kernel@dilger.ca,
jack@suse.com, jaegeuk@kernel.org, linux-ext4@vger.kernel.org,
devel@lists.orangefs.org, hubcap@omnibond.com
Subject: Re: [PATCH v2 2/5] ext4: cache NULL when both default_acl and acl are NULL
Date: Sat, 6 Oct 2018 23:36:45 -0400 [thread overview]
Message-ID: <20181007033645.GA12046@thunk.org> (raw)
In-Reply-To: <f1dd02a3-78ea-0240-72cc-135ee26f6524@gmx.com>
On Wed, Sep 12, 2018 at 11:04:35PM +0800, cgxu519 wrote:
> On 08/31/2018 10:33 PM, Chengguang Xu wrote:
> > default_acl and acl of newly created inode will be initiated
> > as ACL_NOT_CACHED in vfs function inode_init_always() and later
> > will be updated by calling xxx_init_acl() in specific filesystems.
> > Howerver, when default_acl and acl are NULL then they keep the value
> > of ACL_NOT_CACHED, this patch tries to cache NULL for acl/default_acl
> > in this case.
> >
> > Signed-off-by: Chengguang Xu <cgxu519@gmx.com>
Applied, thanks.
- Ted
next prev parent reply other threads:[~2018-10-07 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 14:33 [PATCH v2 1/5] ext2: cache NULL when both default_acl and acl are NULL Chengguang Xu
2018-08-31 14:33 ` [PATCH v2 2/5] ext4: " Chengguang Xu
2018-09-03 8:57 ` Jan Kara
2018-09-12 15:04 ` cgxu519
2018-10-07 3:36 ` Theodore Y. Ts'o [this message]
2018-08-31 14:33 ` [PATCH v2 3/5] f2fs: " Chengguang Xu
2018-09-02 7:55 ` [f2fs-dev] " Chao Yu
2018-09-11 20:12 ` Jaegeuk Kim
2018-08-31 14:33 ` [PATCH v2 4/5] jfs: " Chengguang Xu
2018-09-03 20:34 ` [Jfs-discussion] " Dave Kleikamp
2018-09-05 6:13 ` cgxu519
2018-08-31 14:33 ` [PATCH v2 5/5] orangefs: " Chengguang Xu
2018-09-07 18:11 ` Mike Marshall
2018-09-03 9:03 ` [PATCH v2 1/5] ext2: " Jan Kara
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=20181007033645.GA12046@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=cgxu519@gmx.com \
--cc=devel@lists.orangefs.org \
--cc=hubcap@omnibond.com \
--cc=jack@suse.com \
--cc=jaegeuk@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.com \
--cc=shaggy@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).