From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/5] fs/ntfs3: Some fixes and refactoring
Date: Fri, 1 Jul 2022 16:09:15 +0300 [thread overview]
Message-ID: <34e58f6e-e508-4ad8-6941-37281ea7d3ef@paragon-software.com> (raw)
5 patches with various fixes and refactoring:
- fix for fragmented case
- remove old code
- fix double locking
- hide internal function
- refactor function
Konstantin Komarov (5):
fs/ntfs3: Fix very fragmented case in attr_punch_hole
fs/ntfs3: Remove unused mi_mark_free
fs/ntfs3: Add new argument is_mft to ntfs_mark_rec_free
fs/ntfs3: Make static function attr_load_runs
fs/ntfs3: Fill duplicate info in ni_add_name
fs/ntfs3/attrib.c | 17 ++++++++++++++---
fs/ntfs3/frecord.c | 32 ++++++++++++++++++++------------
fs/ntfs3/fsntfs.c | 9 ++++++---
fs/ntfs3/inode.c | 12 +-----------
fs/ntfs3/namei.c | 2 +-
fs/ntfs3/ntfs_fs.h | 5 +----
fs/ntfs3/record.c | 22 ----------------------
fs/ntfs3/super.c | 2 +-
8 files changed, 44 insertions(+), 57 deletions(-)
--
2.37.0
next reply other threads:[~2022-07-01 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:09 Konstantin Komarov [this message]
2022-07-01 13:09 ` [PATCH 1/5] fs/ntfs3: Fix very fragmented case in attr_punch_hole Konstantin Komarov
2022-07-01 13:10 ` [PATCH 2/5] fs/ntfs3: Remove unused mi_mark_free Konstantin Komarov
2022-07-01 13:10 ` [PATCH 3/5] fs/ntfs3: Add new argument is_mft to ntfs_mark_rec_free Konstantin Komarov
2022-07-01 13:11 ` [PATCH 4/5] fs/ntfs3: Make static function attr_load_runs Konstantin Komarov
2022-07-01 13:11 ` [PATCH 5/5] fs/ntfs3: Fill duplicate info in ni_add_name 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=34e58f6e-e508-4ad8-6941-37281ea7d3ef@paragon-software.com \
--to=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
all inboxes | Powered by JetHome®