From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: fix missing error handling when replaying directory entries
Date: Fri, 1 Oct 2021 13:52:29 +0100 [thread overview]
Message-ID: <cover.1633082623.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Some places during log replay are ignoring errors when looking up directory
entries in a subvolume/fs tree. This fixes all those places and makes sure
we get consistent error hanlding when looking dir items and dir index items.
Filipe Manana (4):
btrfs: deal with errors when checking if a dir entry exists during log replay
btrfs: deal with errors when replaying dir entry during log replay
btrfs: deal with errors when adding inode reference during log replay
btrfs: unify lookup return value when dir entry is missing
fs/btrfs/ctree.h | 2 +-
fs/btrfs/dir-item.c | 48 +++++++++++++++++++++++++--------
fs/btrfs/tree-log.c | 65 ++++++++++++++++++++++++++++-----------------
3 files changed, 79 insertions(+), 36 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-01 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 12:52 fdmanana [this message]
2021-10-01 12:52 ` [PATCH 1/4] btrfs: deal with errors when checking if a dir entry exists during log replay fdmanana
2021-10-01 13:14 ` Qu Wenruo
2021-10-01 14:04 ` Filipe Manana
2021-10-01 12:52 ` [PATCH 2/4] btrfs: deal with errors when replaying dir entry " fdmanana
2021-10-01 12:52 ` [PATCH 3/4] btrfs: deal with errors when adding inode reference " fdmanana
2021-10-01 12:52 ` [PATCH 4/4] btrfs: unify lookup return value when dir entry is missing fdmanana
2021-10-06 12:39 ` [PATCH 0/4] btrfs: fix missing error handling when replaying directory entries 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.1633082623.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.