From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: a couple bug fixes for failures of log replay and mount
Date: Fri, 22 Jan 2021 15:28:33 +0000 [thread overview]
Message-ID: <cover.1611327201.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This small patchset fixes two bugs that lead to an -EINVAL failure during
log replay, causing the filesystem mount to fail. They are relatively new
regressions, one caused by the recent change to make space cache loading
asynchronous and the other caused by the refactoring that made tracking
pinned extents in the transaction instead of tracking them at fs_info.
Filipe Manana (2):
btrfs: fix log replay failure due to race with space cache rebuild
btrfs: fix log replay failure when space cache needs to be rebuilt
fs/btrfs/block-group.c | 15 ++++++++++++---
fs/btrfs/block-group.h | 3 ++-
fs/btrfs/extent-tree.c | 15 +++++++++------
3 files changed, 23 insertions(+), 10 deletions(-)
--
2.28.0
next reply other threads:[~2021-01-22 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 15:28 fdmanana [this message]
2021-01-22 15:28 ` [PATCH 1/2] btrfs: fix log replay failure due to race with space cache rebuild fdmanana
2021-01-22 16:43 ` Josef Bacik
2021-01-22 17:54 ` Filipe Manana
2021-01-22 15:28 ` [PATCH 2/2] btrfs: fix log replay failure when space cache needs to be rebuilt fdmanana
2021-01-22 16:54 ` Josef Bacik
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.1611327201.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