mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <torvalds@linux-foundation.org>
Cc: <ntfs3@lists.linux.dev>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ntfs3: bugfixes for 6.18
Date: Tue, 30 Sep 2025 15:08:33 +0200	[thread overview]
Message-ID: <20250930130833.4866-1-almaz.alexandrovich@paragon-software.com> (raw)

Please pull this branch containing ntfs3 code for 6.18.

Regards,
Konstantin

----------------------------------------------------------------
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  https://github.com/Paragon-Software-Group/linux-ntfs3.git tags/ntfs3_for_6.18

for you to fetch changes up to 7d460636b6402343ca150682f7bae896c4ff2a76:

  ntfs3: stop using write_cache_pages (2025-09-10 11:01:41 +0200)

----------------------------------------------------------------
Changes for 6.18-rc1

Added:
    support for FS_IOC_{GET,SET}FSLABEL ioctl;
    reject index allocation if $BITMAP is empty but blocks exist.

Fixed:
    integer overflow in run_unpack();
    resource leak bug in wnd_extend().

Changed:
    pretend $Extend records as regular files;
    stop using write_cache_pages.

----------------------------------------------------------------
Christoph Hellwig (1):
      ntfs3: stop using write_cache_pages

Ethan Ferguson (3):
      ntfs3: transition magic number to shared constant
      ntfs3: add FS_IOC_GETFSLABEL ioctl
      ntfs3: add FS_IOC_SETFSLABEL ioctl

Haoxiang Li (1):
      fs/ntfs3: Fix a resource leak bug in wnd_extend()

Moon Hee Lee (1):
      fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist

Tetsuo Handa (1):
      ntfs3: pretend $Extend records as regular files

Vitaly Grigoryev (1):
      fs: ntfs3: Fix integer overflow in run_unpack()

 fs/ntfs3/bitmap.c  |  1 +
 fs/ntfs3/file.c    | 28 ++++++++++++++++++++++++++++
 fs/ntfs3/index.c   | 10 ++++++++++
 fs/ntfs3/inode.c   | 16 +++++++++++-----
 fs/ntfs3/ntfs_fs.h |  2 +-
 fs/ntfs3/run.c     | 12 +++++++++---
 6 files changed, 60 insertions(+), 9 deletions(-)

             reply	other threads:[~2025-09-30 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 13:08 Konstantin Komarov [this message]
2025-10-02  1:28 ` Matthew Wilcox
2025-10-03 21:31 ` pr-tracker-bot

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=20250930130833.4866-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 \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®