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
Date: Fri, 24 Sep 2021 13:57:30 +0300 [thread overview]
Message-ID: <20210924105730.2fyzesynznjieddj@kari-VirtualBox> (raw)
In-Reply-To: <a740b507-40d5-0712-af7c-9706d0b11706@paragon-software.com>
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
>
prev parent reply other threads:[~2021-09-24 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 15:38 [PATCH v2 0/6] fs/ntfs3: Refactor locking in inode_operations Konstantin Komarov
2021-09-23 15:40 ` [PATCH v2 1/6] fs/ntfs3: Fix logical error in ntfs_create_inode Konstantin Komarov
2021-09-23 15:42 ` [PATCH v2 2/6] fs/ntfs3: Move ni_lock_dir and ni_unlock into ntfs_create_inode Konstantin Komarov
2021-09-23 15:42 ` [PATCH v2 3/6] fs/ntfs3: Refactor ntfs_get_acl_ex for better readability Konstantin Komarov
2021-09-23 15:43 ` [PATCH v2 4/6] fs/ntfs3: Pass flags to ntfs_set_ea in ntfs_set_acl_ex Konstantin Komarov
2021-09-23 15:44 ` [PATCH v2 5/6] fs/ntfs3: Change posix_acl_equiv_mode to posix_acl_update_mode Konstantin Komarov
2021-09-24 10:55 ` Kari Argillander
2021-09-23 15:45 ` [PATCH v2 6/6] fs/ntfs3: Refactoring lock in ntfs_init_acl Konstantin Komarov
2021-09-24 10:57 ` Kari Argillander [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=20210924105730.2fyzesynznjieddj@kari-VirtualBox \
--to=kari.argillander@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).