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.0-rc5
Date: Mon, 16 Mar 2026 14:04:13 +0100 [thread overview]
Message-ID: <cover.1773665572.git.dsterba@suse.com> (raw)
Hi,
please pull a few more short fixes. Thanks.
- fix logging of new dentries when logging parent directory and there
are conflicting inodes (e.g. deleted directory)
- avoid taking big device lock for zone setup, this is not necessary
during mount
- tune message verbosity when auto-reclaiming zones when low on space
- fix slightly misleading message of root item check
----------------------------------------------------------------
The following changes since commit 0749cab6174dc035b1628fb6db03abf758cfda6f:
btrfs: remove duplicated definition of btrfs_printk_in_rcu() (2026-03-03 17:20:51 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-7.0-rc4-tag
for you to fetch changes up to fc1cd1f18c34f91e78362f9629ab9fd43b9dcab9:
btrfs: tree-checker: fix misleading root drop_level error message (2026-03-13 12:49:25 +0100)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: log new dentries when logging parent dir of a conflicting inode
Johannes Thumshirn (2):
btrfs: pass 'verbose' parameter to btrfs_relocate_block_group
btrfs: don't take device_list_mutex when querying zone info
ZhengYuan Huang (1):
btrfs: tree-checker: fix misleading root drop_level error message
fs/btrfs/tree-checker.c | 2 +-
fs/btrfs/tree-log.c | 6 ++++++
fs/btrfs/volumes.c | 2 +-
fs/btrfs/zoned.c | 6 ++++--
4 files changed, 12 insertions(+), 4 deletions(-)
next reply other threads:[~2026-03-16 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 13:04 David Sterba [this message]
2026-03-16 17:16 ` [GIT PULL] Btrfs fixes for 7.0-rc5 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.1773665572.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.