From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kari.argillander@gmail.com>
Subject: [PATCH v2 0/4] fs/ntfs3: Various fixes for xattr and files
Date: Tue, 26 Oct 2021 19:40:15 +0300 [thread overview]
Message-ID: <a57c1c49-4ef3-15ee-d2cd-d77fb4246b3c@paragon-software.com> (raw)
Various problems were detected by xfstests.
This series aims to fix them.
v2:
- swap patch 3 and 4;
- fixed commit message for patch 1;
- fixed compile error in patch 2.
Konstantin Komarov (4):
fs/ntfs3: Keep preallocated only if option prealloc enabled
fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions
fs/ntfs3: Update i_ctime when xattr is added
fs/ntfs3: Optimize locking in ntfs_save_wsl_perm
fs/ntfs3/file.c | 2 +-
fs/ntfs3/xattr.c | 123 ++++++++++++++++++++++++++++++++++++++++++-----
2 files changed, 113 insertions(+), 12 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-26 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 16:40 Konstantin Komarov [this message]
2021-10-26 16:40 ` [PATCH 1/4] fs/ntfs3: Keep preallocated only if option prealloc enabled Konstantin Komarov
2021-10-26 18:17 ` Kari Argillander
2021-10-26 16:41 ` [PATCH 2/4] fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions Konstantin Komarov
2021-10-26 20:37 ` Kari Argillander
2021-10-27 11:41 ` kernel test robot
2021-10-26 16:41 ` [PATCH 3/4] fs/ntfs3: Update i_ctime when xattr is added Konstantin Komarov
2021-10-26 20:41 ` Kari Argillander
2021-11-15 15:50 ` Konstantin Komarov
2021-10-26 16:42 ` [PATCH 4/4] fs/ntfs3: Optimize locking in ntfs_save_wsl_perm Konstantin Komarov
2021-10-26 18:08 ` Kari Argillander
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=a57c1c49-4ef3-15ee-d2cd-d77fb4246b3c@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=kari.argillander@gmail.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