[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2101d95b-be41-6e6d-e019-bc70f816b2e8@paragon-software.com>
Date: Wed, 13 Jul 2022 19:44:17 +0300
From: Konstantin Komarov <almaz.alexandrovich@...agon-software.com>
To: <ntfs3@...ts.linux.dev>
CC: <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>
Subject: [PATCH 0/6] fs/ntfs3: Refactoring of several functions
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
Powered by blists - more mailing lists