mirror of https://lore.kernel.org/lkml/
 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 7.3-rc4
Date: Sat, 19 Sep 2026 21:44:31 +0200	[thread overview]
Message-ID: <cover.1789845496.git.dsterba@suse.com> (raw)

Hi,

please pull the following fixes. Among the regular fixes, there are two
that were reported recently and have user impact:

- filesystem id is now stable again on the default and common case (it
  broke openconnect key derivation, while this is not secure, it's still
  in use), the intention was to change id for the temp_fsid use case

- fix detection of /dev/root and rename it after device scan, this broke
  booting of initramdisk-less system with grub2 as the probe needs the
  real device

Regular fixes:

- don't store compressed inline extent if the size is larger than
  uncompressed

- in zoned mode, handle activation of zones for all supported block
  group profiles in case there are still free ones left

- check space for a chunk item when reading sys array from superblock

- allow using space reserves when removing verity items fails

- fix error handling after free space tree rebuild fails

- abort transaction if reflink or hole punching fails and it's not
  possible to update the inode

- properly protect block group iteration during device replace start

- error message fixups

----------------------------------------------------------------
The following changes since commit 09f1294ee2abee7fe1c2d600671498b7642e0fe0:

  btrfs: tree-checker: validate name length for extref items (2026-09-07 18:36:38 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-7.3-rc3-tag

for you to fetch changes up to 72de4807ba84da485dda1a91572d66da9149e95a:

  btrfs: derive f_fsid with dev_t only when temp_fsid is active (2026-09-17 19:45:12 +0200)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: derive f_fsid with dev_t only when temp_fsid is active

Daniel Linjama (1):
      btrfs: handle lack of space when cleaning up verity items

Filipe Manana (5):
      btrfs: tree-checker: print dev extent offset in error message
      btrfs: tree-checker: fix error message regarding free space extent items
      btrfs: fix creation of compressed inline extents that don't save space
      btrfs: abort transaction on failure to update inode for hole punching and reflinking
      btrfs: check if there is space for chunk item when validating sys chunk array

Guanghui Yang (1):
      btrfs: clear free space tree creation state on rebuild failure

Hongling Zeng (1):
      btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()

Johannes Thumshirn (1):
      btrfs: zoned: handle RAID profiles in btrfs_can_activate_zone()

Qu Wenruo (1):
      btrfs: add "/dev/root" exception for device path update

 fs/btrfs/dev-replace.c     |  1 +
 fs/btrfs/disk-io.c         |  4 ++++
 fs/btrfs/file.c            |  4 +++-
 fs/btrfs/free-space-tree.c | 14 ++++++++++----
 fs/btrfs/inode.c           | 18 +++++++++++++++++-
 fs/btrfs/super.c           |  8 ++++++--
 fs/btrfs/tree-checker.c    |  4 ++--
 fs/btrfs/verity.c          | 18 ++++++++++++++++--
 fs/btrfs/volumes.c         | 33 ++++++++++++++++++++++++++++++++-
 fs/btrfs/zoned.c           |  5 +++++
 10 files changed, 96 insertions(+), 13 deletions(-)

             reply	other threads:[~2026-09-19 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 19:44 David Sterba [this message]
2026-09-19 19:53 ` Linus Torvalds
2026-09-19 20:46   ` David Sterba
2026-09-19 21:29 ` 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.1789845496.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

all inboxes | Powered by JetHome®