NTFS3 file system kernel mode driver
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Subject: [PATCH v2 0/9] Bugfix and refactoring
Date: Tue, 23 Apr 2024 09:44:19 +0300	[thread overview]
Message-ID: <20240423064428.8289-1-almaz.alexandrovich@paragon-software.com> (raw)

v1->v2:
Here is a reworked series of patches with corrected formatting and layout:
- two patches have been removed for finalization;
- proper commit messages were added;
- important patches have been moved to the beginning of the series
(refactoring at the end).

This series contains various fixes and refactoring for ntfs3.
Fixed problem with incorrect link counting for files with DOS names.

Konstantin Komarov (9):
  fs/ntfs3: Taking DOS names into account during link counting
  fs/ntfs3: Remove max link count info display during driver init
  fs/ntfs3: Missed le32_to_cpu conversion
  fs/ntfs3: Check 'folio' pointer for NULL
  fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow
  fs/ntfs3: Use variable length array instead of fixed size
  fs/ntfs3: Redesign ntfs_create_inode to return error code instead of
    inode
  fs/ntfs3: Always make file nonresident on fallocate call
  fs/ntfs3: Mark volume as dirty if xattr is broken

 fs/ntfs3/attrib.c  | 32 ++++++++++++++++++++++++++++++++
 fs/ntfs3/file.c    |  9 +++++++++
 fs/ntfs3/fslog.c   |  5 +++--
 fs/ntfs3/inode.c   | 46 ++++++++++++++++++++++++++--------------------
 fs/ntfs3/namei.c   | 31 ++++++++-----------------------
 fs/ntfs3/ntfs.h    |  2 +-
 fs/ntfs3/ntfs_fs.h | 10 +++++-----
 fs/ntfs3/record.c  | 11 ++---------
 fs/ntfs3/super.c   |  2 --
 fs/ntfs3/xattr.c   |  5 ++++-
 10 files changed, 90 insertions(+), 63 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-04-23  6:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  6:44 Konstantin Komarov [this message]
2024-04-23  6:44 ` [PATCH 1/9] fs/ntfs3: Taking DOS names into account during link counting Konstantin Komarov
2024-04-23  6:44 ` [PATCH 2/9] fs/ntfs3: Remove max link count info display during driver init Konstantin Komarov
2024-04-23  6:44 ` [PATCH 3/9] fs/ntfs3: Missed le32_to_cpu conversion Konstantin Komarov
2024-04-23  6:44 ` [PATCH 4/9] fs/ntfs3: Check 'folio' pointer for NULL Konstantin Komarov
2024-04-23  6:44 ` [PATCH 5/9] fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow Konstantin Komarov
2024-04-23  6:44 ` [PATCH 6/9] fs/ntfs3: Use variable length array instead of fixed size Konstantin Komarov
2024-04-23  6:44 ` [PATCH 7/9] fs/ntfs3: Redesign ntfs_create_inode to return error code instead of inode Konstantin Komarov
2024-04-23  6:44 ` [PATCH 8/9] fs/ntfs3: Always make file nonresident on fallocate call Konstantin Komarov
2024-04-23  6:44 ` [PATCH 9/9] fs/ntfs3: Mark volume as dirty if xattr is broken 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=20240423064428.8289-1-almaz.alexandrovich@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).