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 fur 6.17-rc7
Date: Wed, 17 Sep 2025 07:20:40 +0200 [thread overview]
Message-ID: <cover.1758085289.git.dsterba@suse.com> (raw)
Hi,
please pull a few more btrfs fixes. Thanks.
- in zoned mode, turn assertion to proper code when reserving space in
relocation block group
- fix search key of extended ref (hardlink) when replaying log
- fix initialization of file extent tree on filesystems without no-holes
feature
- add harmless data race annotation to block group comparator
----------------------------------------------------------------
The following changes since commit 3d1267475b94b3df7a61e4ea6788c7c5d9e473c4:
btrfs: don't allow adding block device of less than 1 MB (2025-09-05 19:52:10 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc6-tag
for you to fetch changes up to 80eb65ccf6f72dc37b972583fe71cd8a50ff7e51:
btrfs: annotate block group access with data_race() when sorting for reclaim (2025-09-15 05:25:43 +0200)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: fix invalid extref key setup when replaying dentry
btrfs: annotate block group access with data_race() when sorting for reclaim
Johannes Thumshirn (1):
btrfs: zoned: fix incorrect ASSERT in btrfs_zoned_reserve_data_reloc_bg()
austinchang (1):
btrfs: initialize inode::file_extent_tree after i_mode has been set
fs/btrfs/block-group.c | 9 ++++++++-
fs/btrfs/delayed-inode.c | 3 ---
fs/btrfs/inode.c | 11 +++++------
fs/btrfs/tree-log.c | 2 +-
fs/btrfs/zoned.c | 2 +-
5 files changed, 15 insertions(+), 12 deletions(-)
next reply other threads:[~2025-09-17 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 5:20 David Sterba [this message]
2025-09-17 18:38 ` [GIT PULL] Btrfs fixes fur 6.17-rc7 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.1758085289.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;
as well as URLs for NNTP newsgroup(s).