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.17-rc2
Date: Tue, 12 Aug 2025 14:26:32 +0200 [thread overview]
Message-ID: <cover.1755000200.git.dsterba@suse.com> (raw)
Hi,
please pull a few regression fixes and other usual fixes. Thanks.
- fix bug in qgroups reporting incorrect usage for higher level qgroups
- in zoned mode, do not select metadata group as finish target
- convert xarray lock to RCU when trying to release extent buffer to
avoid a deadlock
- do not allow relocation on partially dropped subvolumes, which is
normally not possible but has been reported on old filesystems
- in tree-log, report errors on missing block group when unaccounting
log tree extent buffers
- with large folios, fix range length when processing ordered extents
----------------------------------------------------------------
The following changes since commit 0a32e4f0025a74c70dcab4478e9b29c22f5ecf2f:
btrfs: fix log tree replay failure due to file with 0 links and extents (2025-08-06 13:01:38 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc1-tag
for you to fetch changes up to 7b632596188e1973c6b3ac1c9f8252f735e1039f:
btrfs: fix iteration bug in __qgroup_excl_accounting() (2025-08-07 17:07:16 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix iteration bug in __qgroup_excl_accounting()
Filipe Manana (1):
btrfs: error on missing block group when unaccounting log tree extent buffers
Leo Martins (1):
btrfs: fix subpage deadlock in try_release_subpage_extent_buffer()
Naohiro Aota (1):
btrfs: zoned: do not select metadata BG as finish target
Qu Wenruo (3):
btrfs: make btrfs_cleanup_ordered_extents() support large folios
btrfs: fix wrong length parameter for btrfs_cleanup_ordered_extents()
btrfs: do not allow relocation of partially dropped subvolumes
fs/btrfs/extent_io.c | 11 ++++++-----
fs/btrfs/inode.c | 8 +++++---
fs/btrfs/qgroup.c | 3 +--
fs/btrfs/relocation.c | 19 +++++++++++++++++++
fs/btrfs/tree-log.c | 19 +++++++------------
fs/btrfs/zoned.c | 2 +-
6 files changed, 39 insertions(+), 23 deletions(-)
next reply other threads:[~2025-08-12 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:26 David Sterba [this message]
2025-08-12 16:00 ` 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.1755000200.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®