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-rc3
Date: Sat, 12 Sep 2026 15:37:14 +0200 [thread overview]
Message-ID: <cover.1789169569.git.dsterba@suse.com> (raw)
Hi,
please pull a few small fixes. Thanks.
- tree-checker updates, validate values in b-tree item keys, other item
length checks
- don't do unnecessary transaction commit fallback when logging parent
directories
- in zoned mode, initialize space info of a block group early enough so
it does not lead to NULL pointer dereference
----------------------------------------------------------------
The following changes since commit 6a7a45b1d94799a5eb8e6d26e65cf31a3fcda9e5:
MAINTAINERS: update Chris Mason's email address (2026-09-02 22:19:30 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-7.3-rc2-tag
for you to fetch changes up to 09f1294ee2abee7fe1c2d600671498b7642e0fe0:
btrfs: tree-checker: validate name length for extref items (2026-09-07 18:36:38 +0200)
----------------------------------------------------------------
Filipe Manana (4):
btrfs: fix unnecessary transaction commit fallback from btrfs_log_all_parents()
btrfs: tree-checker: validate key offset for inode ref keys
btrfs: tree-checker: validate parent field for inode extref items
btrfs: tree-checker: validate name length for extref items
Johannes Thumshirn (1):
btrfs: set space_info before adding new free space in btrfs_make_block_group()
fs/btrfs/block-group.c | 20 ++++++++++++--------
fs/btrfs/tree-checker.c | 29 +++++++++++++++++++++++++++++
fs/btrfs/tree-log.c | 16 ++++++++++++++++
3 files changed, 57 insertions(+), 8 deletions(-)
next reply other threads:[~2026-09-12 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 13:37 David Sterba [this message]
2026-09-12 16:16 ` 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.1789169569.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®