From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>, LKML <linux-kernel@vger.kernel.org>,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 00/11] Bugfix and refactoring
Date: Wed, 17 Apr 2024 16:03:46 +0300 [thread overview]
Message-ID: <6c99c1bd-448d-4301-8404-50df34e8df8e@paragon-software.com> (raw)
This series contains various fixes and refactoring for ntfs3.
Fixed problem with incorrect link counting for files with DOS names.
Konstantin Komarov (11):
fs/ntfs3: Remove max link count info display during driver init
fs/ntfs3: Missed le32_to_cpu conversion
fs/ntfs3: Mark volume as dirty if xattr is broken
fs/ntfs3: Use variable length array instead of fixed size
fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow
fs/ntfs3: Redesign ntfs_create_inode to return error code instead of
inode
fs/ntfs3: Check 'folio' pointer for NULL
fs/ntfs3: Always make file nonresident if fallocate (xfstest 438)
fs/ntfs3: Optimize to store sorted attribute definition table
fs/ntfs3: Remove cached label from sbi
fs/ntfs3: Taking DOS names into account during link counting
fs/ntfs3/attrib.c | 103 ++++++++++++++++++++++++++++++++
fs/ntfs3/file.c | 9 +++
fs/ntfs3/fslog.c | 5 +-
fs/ntfs3/fsntfs.c | 77 ++++++++++++++++++++----
fs/ntfs3/inode.c | 76 ++++++++++++-----------
fs/ntfs3/namei.c | 31 +++-------
fs/ntfs3/ntfs.h | 6 +-
fs/ntfs3/ntfs_fs.h | 77 +++++++++++++++---------
fs/ntfs3/record.c | 11 +---
fs/ntfs3/super.c | 146 +++++++++++++++++++--------------------------
fs/ntfs3/xattr.c | 23 ++++---
11 files changed, 355 insertions(+), 209 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-17 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 13:03 Konstantin Komarov [this message]
2024-04-17 13:04 ` [PATCH 01/11] fs/ntfs3: Remove max link count info display during driver init Konstantin Komarov
2024-04-17 13:04 ` [PATCH 02/11] fs/ntfs3: Missed le32_to_cpu conversion Konstantin Komarov
2024-04-17 13:06 ` [PATCH 03/11] fs/ntfs3: Mark volume as dirty if xattr is broken Konstantin Komarov
2024-04-17 13:06 ` [PATCH 04/11] fs/ntfs3: Use variable length array instead of fixed size Konstantin Komarov
2024-04-17 13:06 ` [PATCH 05/11] fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow Konstantin Komarov
2024-04-17 13:07 ` [PATCH 06/11] fs/ntfs3: Redesign ntfs_create_inode to return error code instead of inode Konstantin Komarov
2024-04-17 13:07 ` [PATCH 07/11] fs/ntfs3: Check 'folio' pointer for NULL Konstantin Komarov
2024-04-17 13:08 ` [PATCH 08/11] fs/ntfs3: Always make file nonresident if fallocate (xfstest 438) Konstantin Komarov
2024-04-17 13:08 ` [PATCH 09/11] fs/ntfs3: Optimize to store sorted attribute definition table Konstantin Komarov
2024-04-17 13:09 ` [PATCH 10/11] fs/ntfs3: Remove cached label from sbi Konstantin Komarov
2024-04-22 20:42 ` Nathan Chancellor
2024-04-17 13:10 ` [PATCH 11/11] fs/ntfs3: Taking DOS names into account during link counting Konstantin Komarov
2024-04-18 6:31 ` Johan Hovold
2024-04-23 6:59 ` Konstantin Komarov
2024-04-18 6:42 ` [PATCH 00/11] Bugfix and refactoring Johan Hovold
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=6c99c1bd-448d-4301-8404-50df34e8df8e@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).