From: cgxu519 <cgxu519@gmx.com>
To: Dave Kleikamp <dave.kleikamp@oracle.com>,
jack@suse.com, tytso@mit.edu, adilger.kernel@dilger.ca,
jaegeuk@kernel.org, yuchao0@huawei.com, shaggy@kernel.org,
hubcap@omnibond.com, martin@omnibond.com
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org, devel@lists.orangefs.org
Subject: Re: [Jfs-discussion] [PATCH v2 4/5] jfs: cache NULL when both default_acl and acl are NULL
Date: Wed, 5 Sep 2018 14:13:47 +0800 [thread overview]
Message-ID: <c231d198-7a4e-63a0-0a7d-9211ab0abfe9@gmx.com> (raw)
In-Reply-To: <0e37733e-9acd-cf82-62f7-420f0fa864eb@oracle.com>
On 09/04/2018 04:34 AM, Dave Kleikamp wrote:
> Are you pushing these as a series, or would you like this patch pushed
> through the jfs tree?
I'd hope maintainers pick individual patch to their tree.
Thanks,
Chengguang
>
> On 8/31/18 9:33 AM, 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>
> Acked-by: Dave Kleikamp <dave.kleikamp@oracle.com>
>
next prev parent reply other threads:[~2018-09-05 6:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 14:33 [PATCH v2 1/5] ext2: " 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
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 [this message]
2018-09-05 12:28 ` Dave Kleikamp
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=c231d198-7a4e-63a0-0a7d-9211ab0abfe9@gmx.com \
--to=cgxu519@gmx.com \
--cc=adilger.kernel@dilger.ca \
--cc=dave.kleikamp@oracle.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 \
--cc=tytso@mit.edu \
--cc=yuchao0@huawei.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
all inboxes | Powered by JetHome®