public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.18-rc3
Date: Thu, 23 Oct 2025 09:16:23 +0200	[thread overview]
Message-ID: <cover.1761202410.git.dsterba@suse.com> (raw)

Hi,

please pull a few btrfs fixes. Thanks.

- in send, fix duplicated rmdir operations when using extrefs
  (hardlinks), receive can fail with ENOENT

- fixup of error check when reading extent root in ref-verify and
  damaged roots are allowed by mount option (found by smatch)

- fix freeing partially initialized fs info (found by syzkaller)

- fix use-after-free when printing ref_tracking status of delayed inodes

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

  btrfs: send: fix -Wflex-array-member-not-at-end warning in struct send_ctx (2025-10-13 22:36:38 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.18-rc2-tag

for you to fetch changes up to ada7d45b568abe4f1fd9c53d66e05fbea300674b:

  btrfs: ref-verify: fix IS_ERR() vs NULL check in btrfs_build_ref_tree() (2025-10-22 09:40:07 +0200)

----------------------------------------------------------------
Amit Dhingra (1):
      btrfs: ref-verify: fix IS_ERR() vs NULL check in btrfs_build_ref_tree()

Dewei Meng (1):
      btrfs: directly free partially initialized fs_info in btrfs_check_leaked_roots()

Leo Martins (1):
      btrfs: fix delayed_node ref_tracker use after free

Ting-Chang Hou (1):
      btrfs: send: fix duplicated rmdir operations when using extrefs

 fs/btrfs/delayed-inode.c |  2 +-
 fs/btrfs/delayed-inode.h |  7 ++++++
 fs/btrfs/ref-verify.c    |  2 +-
 fs/btrfs/send.c          | 56 +++++++++++++++++++++++++++++++++++++++++-------
 fs/btrfs/super.c         |  8 ++++++-
 5 files changed, 64 insertions(+), 11 deletions(-)

             reply	other threads:[~2025-10-23  7:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  7:16 David Sterba [this message]
2025-10-23 17:03 ` [GIT PULL] Btrfs fixes for 6.18-rc3 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=cover.1761202410.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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