Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 24 Sep 2021 13:57:30 +0300
From:   Kari Argillander <kari.argillander@gmail.com>
To:     Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc:     ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
        linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] fs/ntfs3: Refactor locking in inode_operations
Message-ID: <20210924105730.2fyzesynznjieddj@kari-VirtualBox>
References: <a740b507-40d5-0712-af7c-9706d0b11706@paragon-software.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a740b507-40d5-0712-af7c-9706d0b11706@paragon-software.com>
Precedence: bulk

On Thu, Sep 23, 2021 at 06:38:39PM +0300, Konstantin Komarov wrote:
> Speed up work with dir lock.
> Theoretically in successful cases those locks aren't needed at all.
> But proving the same for error cases is difficult.
> So instead of removing them we just move them.
> 
> V2:
>   added patch, that fixes logical error in ntfs_create_inode

Whole series

Reviewed-by: Kari Argillander <kari.argillander@gmail.com>

> 
> Konstantin Komarov (6):
>   fs/ntfs3: Fix logical error in ntfs_create_inode
>   fs/ntfs3: Move ni_lock_dir and ni_unlock into ntfs_create_inode
>   fs/ntfs3: Refactor ntfs_get_acl_ex for better readability
>   fs/ntfs3: Pass flags to ntfs_set_ea in ntfs_set_acl_ex
>   fs/ntfs3: Change posix_acl_equiv_mode to posix_acl_update_mode
>   fs/ntfs3: Refactoring lock in ntfs_init_acl
> 
>  fs/ntfs3/inode.c | 19 ++++++++---
>  fs/ntfs3/namei.c | 20 -----------
>  fs/ntfs3/xattr.c | 88 +++++++++++++++++-------------------------------
>  3 files changed, 46 insertions(+), 81 deletions(-)
> 
> -- 
> 2.33.0
>