mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 glaubitz@physik.fu-berlin.de, frank.li@vivo.com,
	johannes.thumshirn@wdc.com, 	penguin-kernel@I-love.SAKURA.ne.jp
Subject: [GIT PULL] hfs/hfsplus changes for 6.17-rc1
Date: Mon, 28 Jul 2025 11:43:32 -0700	[thread overview]
Message-ID: <a557f6d129ea4cb7ab1d1ed2232bfa811810abe2.camel@dubeyko.com> (raw)

Hello Linus,

Currently, we have around 221 opened issues in HFS/HFS+ file system
drivers. Mostly, xfstests reveal majority of the issues and multiple
tests leave HFS/HFS+ volume in corrupted state.

Johannes Thumshirn has made nice cleanup in hfsplus_submit_bio().
Tetsuo Handa has fixed the syzbot reported issue in
hfsplus_create_attributes_file() for the case of corruption
the Attributes File's metadata. Yangtao Li has fixed the syzbot
reported issue by removing the uneccessary WARN_ON() in
hfsplus_free_extents().

The rest patches contains fixes:
(1) restoring generic/001 successful execution by erasing
deleted b-tree nodes;
(2) eliminating slab-out-of-bounds issue in hfs_bnode_read()
and hfsplus_bnode_read() by checking correctness of offset and
length by operation of accessing b-tree node's content;
(3) eliminating slab-out-of-bounds read in hfsplus_uni2asc()
for the case if b-tree node's record has corrupted length of
a name that could be bigger than HFSPLUS_MAX_STRLEN;
(4) eliminating general protection fault in hfs_find_init()
for the case of initial b-tree object creation.

The following changes since commit
19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git
tags/hfs-v6.17-tag1

for you to fetch changes up to
736a0516a16268995f4898eded49bfef077af709:

  hfs: fix general protection fault in hfs_find_init() (2025-07-25
15:40:16 -0700)

----------------------------------------------------------------
hfs/hfsplus updates for v6.17

- hfs: fix general protection fault in hfs_find_init()
- hfs: fix slab-out-of-bounds in hfs_bnode_read()
- hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()
- hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()
- hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
- hfsplus: don't set REQ_SYNC for hfsplus_submit_bio()
- hfsplus: remove mutex_lock check in hfsplus_free_extents
- hfs: make splice write available again
- hfsplus: make splice write available again
- hfs: fix not erasing deleted b-tree node issue

----------------------------------------------------------------
Johannes Thumshirn (1):
      hfsplus: don't set REQ_SYNC for hfsplus_submit_bio()

Tetsuo Handa (1):
      hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()

Viacheslav Dubeyko (5):
      hfs: fix not erasing deleted b-tree node issue
      hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()
      hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()
      hfs: fix slab-out-of-bounds in hfs_bnode_read()
      hfs: fix general protection fault in hfs_find_init()

Yangtao Li (3):
      hfsplus: make splice write available again
      hfs: make splice write available again
      hfsplus: remove mutex_lock check in hfsplus_free_extents

 fs/hfs/bfind.c       |  3 ++
 fs/hfs/bnode.c       | 93
++++++++++++++++++++++++++++++++++++++++++++++++++++
 fs/hfs/btree.c       | 57 +++++++++++++++++++++++++-------
 fs/hfs/extent.c      |  2 +-
 fs/hfs/hfs_fs.h      |  1 +
 fs/hfs/inode.c       |  1 +
 fs/hfsplus/bnode.c   | 92
+++++++++++++++++++++++++++++++++++++++++++++++++++
 fs/hfsplus/extents.c |  3 --
 fs/hfsplus/inode.c   |  1 +
 fs/hfsplus/super.c   |  6 ++--
 fs/hfsplus/unicode.c |  7 ++++
 fs/hfsplus/xattr.c   |  6 +++-
 12 files changed, 252 insertions(+), 20 deletions(-)

             reply	other threads:[~2025-07-28 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 18:43 Viacheslav Dubeyko [this message]
2025-07-28 23:41 ` 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=a557f6d129ea4cb7ab1d1ed2232bfa811810abe2.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --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®