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 00/14] fs/ntfs3: Additional bugfix and refactoring
Date: Fri, 28 Oct 2022 20:00:40 +0300 [thread overview]
Message-ID: <fc5957cc-a71b-cfa3-f291-cb63b23800d1@paragon-software.com> (raw)
Second part of various fixes and refactoring for ntfs3.
Konstantin Komarov (14):
fs/ntfs3: Fixing work with sparse clusters
fs/ntfs3: Change new sparse cluster processing
fs/ntfs3: Fix wrong indentations
fs/ntfs3: atomic_open implementation
fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate
fs/ntfs3: Changing locking in ntfs_rename
fs/ntfs3: Restore correct state after ENOSPC in attr_data_get_block
fs/ntfs3: Correct ntfs_check_for_free_space
fs/ntfs3: Check fields while reading
fs/ntfs3: Fix incorrect if in ntfs_set_acl_ex
fs/ntfs3: Use ALIGN kernel macro
fs/ntfs3: Fix wrong if in hdr_first_de
fs/ntfs3: Improve checking of bad clusters
fs/ntfs3: Make if more readable
fs/ntfs3/attrib.c | 338 +++++++++++++++++++++++++++++----------------
fs/ntfs3/bitmap.c | 38 +++++
fs/ntfs3/file.c | 203 ++++++++-------------------
fs/ntfs3/frecord.c | 2 +-
fs/ntfs3/fslog.c | 3 +-
fs/ntfs3/fsntfs.c | 35 ++++-
fs/ntfs3/index.c | 105 ++++++++++++--
fs/ntfs3/inode.c | 86 +++++++-----
fs/ntfs3/namei.c | 104 ++++++++++++++
fs/ntfs3/ntfs.h | 6 +-
fs/ntfs3/ntfs_fs.h | 22 ++-
fs/ntfs3/record.c | 5 +-
fs/ntfs3/run.c | 28 +---
fs/ntfs3/super.c | 64 +++++----
fs/ntfs3/xattr.c | 116 ++++++++++------
15 files changed, 737 insertions(+), 418 deletions(-)
--
2.37.0
next reply other threads:[~2022-10-28 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 17:00 Konstantin Komarov [this message]
2022-10-28 17:01 ` [PATCH 01/14] fs/ntfs3: Fixing work with sparse clusters Konstantin Komarov
2022-10-28 17:02 ` [PATCH 02/14] fs/ntfs3: Change new sparse cluster processing Konstantin Komarov
2022-10-28 17:02 ` [PATCH 03/14] fs/ntfs3: Fix wrong indentations Konstantin Komarov
2022-10-28 17:03 ` [PATCH 04/14] fs/ntfs3: atomic_open implementation Konstantin Komarov
2022-10-28 17:03 ` [PATCH 05/14] fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate Konstantin Komarov
2022-10-28 17:04 ` [PATCH 06/14] fs/ntfs3: Changing locking in ntfs_rename Konstantin Komarov
2022-10-28 17:04 ` [PATCH 07/14] fs/ntfs3: Restore correct state after ENOSPC in attr_data_get_block Konstantin Komarov
2022-10-28 17:05 ` [PATCH 08/14] fs/ntfs3: Correct ntfs_check_for_free_space Konstantin Komarov
2022-10-28 17:05 ` [PATCH 09/14] fs/ntfs3: Check fields while reading Konstantin Komarov
2023-06-19 9:41 ` Lee Jones
2023-06-27 13:49 ` Lee Jones
2022-10-28 17:06 ` [PATCH 10/14] fs/ntfs3: Fix incorrect if in ntfs_set_acl_ex Konstantin Komarov
2022-10-28 17:06 ` [PATCH 11/14] fs/ntfs3: Use ALIGN kernel macro Konstantin Komarov
2022-10-28 17:07 ` [PATCH 12/14] fs/ntfs3: Fix wrong if in hdr_first_de Konstantin Komarov
2022-10-28 17:07 ` [PATCH 13/14] fs/ntfs3: Improve checking of bad clusters Konstantin Komarov
2022-10-28 17:08 ` [PATCH 14/14] fs/ntfs3: Make if more readable 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=fc5957cc-a71b-cfa3-f291-cb63b23800d1@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 read-only IMAP folder(s) and NNTP newsgroup(s).