From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/3] btrfs: log replay bug fixes and cleanup
Date: Fri, 11 Jul 2025 21:36:37 +0100 [thread overview]
Message-ID: <cover.1752266047.git.fdmanana@suse.com> (raw)
In-Reply-To: <cover.1752265165.git.fdmanana@suse.com>
From: Filipe Manana <fdmanana@suse.com>
A couple bug fixes for log replay and a cleanup.
V2: Updated patch 2/3 to avoid a NULL pointer deref on directory.
Filipe Manana (3):
btrfs: don't ignore inode missing when replaying log tree
btrfs: don't skip remaining extrefs if dir not found during log replay
btrfs: use saner variable type and name to indicate extrefs at add_inode_ref()
fs/btrfs/tree-log.c | 37 ++++++++++++++++++++++++++++---------
1 file changed, 28 insertions(+), 9 deletions(-)
--
2.47.2
next prev parent reply other threads:[~2025-07-11 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 20:26 [PATCH 0/3] btrfs: log replay bug fixes and cleanup fdmanana
2025-07-11 20:26 ` [PATCH 1/3] btrfs: don't ignore inode missing when replaying log tree fdmanana
2025-07-11 20:26 ` [PATCH 2/3] btrfs: don't skip remaining extrefs if dir not found during log replay fdmanana
2025-07-11 20:26 ` [PATCH 3/3] btrfs: use saner variable type and name to indicate extrefs at add_inode_ref() fdmanana
2025-07-11 20:36 ` fdmanana [this message]
2025-07-11 20:36 ` [PATCH v2 1/3] btrfs: don't ignore inode missing when replaying log tree fdmanana
2025-07-11 20:36 ` [PATCH v2 2/3] btrfs: don't skip remaining extrefs if dir not found during log replay fdmanana
2025-07-11 20:36 ` [PATCH v2 3/3] btrfs: use saner variable type and name to indicate extrefs at add_inode_ref() fdmanana
2025-07-17 17:53 ` [PATCH v2 0/3] btrfs: log replay bug fixes and cleanup Boris Burkov
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.1752266047.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.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