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.1-rc2
Date: Mon, 27 Apr 2026 17:04:29 +0200 [thread overview]
Message-ID: <cover.1777300791.git.dsterba@suse.com> (raw)
Hi,
please pull the following batch of fixes that arrived shortly before or
during the merge window.
Thanks.
- space reservation fixes
- correctly undo 'may_use' accounting for remap tree
- avoid double decrement of 'may_use' when submitting async io
- actually enable the shutdown ioctl callback (not just the superblock ops)
- raid stripe tree fixes when deleting extents
- add missing error handling
- fix various incorrect values set
- fix transaction state when removing a directory, possibly leading to
EIO during log replay
- additional b-tree node key checks during metadata readahead
- error handling and transaction abort updates
----------------------------------------------------------------
The following changes since commit fc3d53288158d68444eed059adb734709b855bbf:
btrfs: btrfs_log_dev_io_error() on all bio errors (2026-04-07 20:00:29 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-7.1-rc1-tag
for you to fetch changes up to 82323b1a7088b7a5c3e528a5d634bff447fa286f:
btrfs: fix double-decrement of bytes_may_use in submit_one_async_extent() (2026-04-21 04:03:08 +0200)
----------------------------------------------------------------
David Sterba (1):
btrfs: handle unexpected free-space-tree key types
Filipe Manana (1):
btrfs: fix missing last_unlink_trans update when removing a directory
Mark Harmstone (5):
btrfs: fix bytes_may_use leak in move_existing_remap()
btrfs: fix bytes_may_use leak in do_remap_reloc_trans()
btrfs: abort transaction in do_remap_reloc_trans() on failure
btrfs: don't clobber errors in add_remap_tree_entries()
btrfs: fix double-decrement of bytes_may_use in submit_one_async_extent()
Qu Wenruo (2):
btrfs: apply first key check for readahead when possible
btrfs: enable shutdown ioctl for non-experimental builds
robbieko (6):
btrfs: copy devid in btrfs_partially_delete_raid_extent()
btrfs: fix raid stripe search missing entries at leaf boundaries
btrfs: fix wrong min_objectid in btrfs_previous_item() call
btrfs: replace ASSERT with proper error handling in stripe lookup fallback
btrfs: handle -EAGAIN from btrfs_duplicate_item and refresh stale leaf pointer
btrfs: check return value of btrfs_partially_delete_raid_extent()
fs/btrfs/extent_io.c | 14 +++++++++--
fs/btrfs/extent_io.h | 3 ++-
fs/btrfs/free-space-tree.c | 18 +++++++++++---
fs/btrfs/inode.c | 4 +++-
fs/btrfs/ioctl.c | 7 +++---
fs/btrfs/raid-stripe-tree.c | 57 +++++++++++++++++++++++++++++++++++----------
fs/btrfs/relocation.c | 30 +++++++++++++++++++-----
7 files changed, 104 insertions(+), 29 deletions(-)
next reply other threads:[~2026-04-27 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 15:04 David Sterba [this message]
2026-04-27 23:53 ` [GIT PULL] Btrfs fixes for 7.1-rc2 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.1777300791.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.