From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: a couple fixes for log replay and a refactoring
Date: Mon, 1 Aug 2022 14:57:50 +0100 [thread overview]
Message-ID: <cover.1659361747.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Fix two minor issues during log replay, when processing inode references,
and rework a bit the processing of new inode references to remove some
special code for special cases.
Filipe Manana (3):
btrfs: fix lost error handling when looking up extended ref on log
replay
btrfs: fix warning during log replay when bumping inode link count
btrfs: simplify adding and replacing references during log replay
fs/btrfs/tree-log.c | 168 +++++---------------------------------------
1 file changed, 16 insertions(+), 152 deletions(-)
--
2.35.1
next reply other threads:[~2022-08-01 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:57 fdmanana [this message]
2022-08-01 13:57 ` [PATCH 1/3] btrfs: fix lost error handling when looking up extended ref on log replay fdmanana
2022-08-01 13:57 ` [PATCH 2/3] btrfs: fix warning during log replay when bumping inode link count fdmanana
2022-08-01 13:57 ` [PATCH 3/3] btrfs: simplify adding and replacing references during log replay fdmanana
2022-08-03 20:05 ` [PATCH 0/3] btrfs: a couple fixes for log replay and a refactoring David Sterba
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.1659361747.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 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.