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/6] fs/ntfs3: Refactoring of several functions
Date: Wed, 13 Jul 2022 19:44:17 +0300 [thread overview]
Message-ID: <2101d95b-be41-6e6d-e019-bc70f816b2e8@paragon-software.com> (raw)
6 commits, that hopefully improves code (tests are ok).
While working on attr_set_size, attr_punch_hole and attr_insert_range
I've noticed how convoluted the code is.
I'll think about how to make code less complex.
Konstantin Komarov (6):
fs/ntfs3: New function ntfs_bad_inode
fs/ntfs3: Refactoring attr_set_size to restore after errors
fs/ntfs3: Refactoring attr_punch_hole to restore after errors
fs/ntfs3: Refactoring attr_insert_range to restore after errors
fs/ntfs3: Create MFT zone only if length is large enough
fs/ntfs3: ni_ins_new_attr now returns error
fs/ntfs3/attrib.c | 416 +++++++++++++++++++++++++++++++--------------
fs/ntfs3/frecord.c | 35 +++-
fs/ntfs3/fsntfs.c | 25 ++-
fs/ntfs3/inode.c | 6 +-
fs/ntfs3/namei.c | 4 +-
fs/ntfs3/ntfs_fs.h | 3 +
fs/ntfs3/run.c | 25 +++
7 files changed, 368 insertions(+), 146 deletions(-)
--
2.37.0
next reply other threads:[~2022-07-13 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 16:44 Konstantin Komarov [this message]
2022-07-13 16:45 ` [PATCH 1/6] fs/ntfs3: New function ntfs_bad_inode Konstantin Komarov
2022-07-13 16:45 ` [PATCH 2/6] fs/ntfs3: Refactoring attr_set_size to restore after errors Konstantin Komarov
2022-07-13 16:46 ` [PATCH 3/6] fs/ntfs3: Refactoring attr_punch_hole " Konstantin Komarov
2022-07-13 18:58 ` Joe Perches
2022-07-13 16:46 ` [PATCH 4/6] fs/ntfs3: Refactoring attr_insert_range " Konstantin Komarov
2022-07-13 16:47 ` [PATCH 5/6] fs/ntfs3: Create MFT zone only if length is large enough Konstantin Komarov
2022-07-13 16:47 ` [PATCH 6/6] fs/ntfs3: Make ni_ins_new_attr return error 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=2101d95b-be41-6e6d-e019-bc70f816b2e8@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;
as well as URLs for NNTP newsgroup(s).