All of lore.kernel.org
 help / color / mirror / Atom feed
From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Kari Argillander <kari.argillander@gmail.com>
Cc: "almaz.alexandrovich@paragon-software.com"
	<almaz.alexandrovich@paragon-software.com>,
	"ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>
Subject: Re: [RFC] ntfs3: Use the same order for acl pointer check in ntfs_init_acl
Date: Thu, 21 Apr 2022 09:17:30 +0000	[thread overview]
Message-ID: <62612F86.6070502@fujitsu.com> (raw)
In-Reply-To: <ad6d9ad3-1b9d-5e18-6d80-039680c5bede@gmail.com>

on 2022/4/21 17:05, Kari Argillander wrote:
> On 21.4.2022 4.57, xuyang2018.jy@fujitsu.com wrote:
>> on 2022/4/21 1:43, Kari Argillander wrote:
>>> I do not understand why this RFC and not a patch.
>> I don't sure whether this small nit is a problem and can be accepted by
>> nfs3 group. So When generate a patch, I add RFC subject for it.
>
> RFC means request for comments. Usually this means that patch needs more
> work but I would like to discuss this topic before I continue this work.
> This was small nit and is no problem, but I just wanted to point that
> out.

Thanks, now I understand.

>
> Argillander
>
>>> On 20.4.2022 11.48, Yang Xu wrote:
>>>> Like ext4 and other use ${fs}_init_acl filesystem, they all used the
>>>> following
>>>> style
>>>>
>>>> error = posix_acl_create(dir, &inode->i_mode, &default_acl, &acl);
>>>> if (error)
>>>> return error;
>>>>
>>>> if (default_acl) {
>>>> error = __ext4_set_acl(handle, inode, ACL_TYPE_DEFAULT,
>>>> default_acl, XATTR_CREATE);
>>>> posix_acl_release(default_acl);
>>>> } else {
>>>> inode->i_default_acl = NULL;
>>>> }
>>>> if (acl) {
>>>> if (!error)
>>>> error = __ext4_set_acl(handle, inode, ACL_TYPE_ACCESS,
>>>> acl, XATTR_CREATE);
>>>> posix_acl_release(acl);
>>>> } else {
>>>> inode->i_acl = NULL;
>>>> }
>>>> ...
>>>>
>>>> So for the readability and unity of the code, adjust this order.
>>>>
>>>> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
>>> Reviewed-by: Kari Argillander <kari.argillander@gmail.com>
>>>
>>>> ---
>>>> fs/ntfs3/xattr.c | 6 +++---
>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/fs/ntfs3/xattr.c b/fs/ntfs3/xattr.c
>>>> index afd0ddad826f..64cefa869a61 100644
>>>> --- a/fs/ntfs3/xattr.c
>>>> +++ b/fs/ntfs3/xattr.c
>>>> @@ -642,13 +642,13 @@ int ntfs_init_acl(struct user_namespace
>>>> *mnt_userns, struct inode *inode,
>>>> inode->i_default_acl = NULL;
>>>> }
>>>> - if (!acl)
>>>> - inode->i_acl = NULL;
>>>> - else {
>>>> + if (acl) {
>>>> if (!err)
>>>> err = ntfs_set_acl_ex(mnt_userns, inode, acl,
>>>> ACL_TYPE_ACCESS);
>>>> posix_acl_release(acl);
>>>> + } else {
>>>> + inode->i_acl = NULL;
>>>> }
>>>> return err;

  reply	other threads:[~2022-04-21  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  8:48 [RFC] ntfs3: Use the same order for acl pointer check in ntfs_init_acl Yang Xu
2022-04-20 17:43 ` Kari Argillander
2022-04-21  1:57   ` xuyang2018.jy
2022-04-21  9:05     ` Kari Argillander
2022-04-21  9:17       ` xuyang2018.jy [this message]
2022-06-09 16:22 ` Konstantin Komarov

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=62612F86.6070502@fujitsu.com \
    --to=xuyang2018.jy@fujitsu.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=kari.argillander@gmail.com \
    --cc=ntfs3@lists.linux.dev \
    /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.