From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/3] btrfs: fix generic/475 hang
Date: Thu, 20 Jul 2023 16:12:13 -0400 [thread overview]
Message-ID: <cover.1689883754.git.josef@toxicpanda.com> (raw)
Hello,
With the new GH CI setup we were seeing consistent hangs with generic/475. This
was a pretty subtle and unique hang that's described in the first patch. I've
included the patch first to make it easier to backport for those who wish to do
so, this bug has existed forever, though is really very specific to the use of
dmsetup suspend. Before this patch I couldn't make it through 10 loops of
generic/475 in my VM, with it I've been running it in a loop for an hour with no
problems. The series is currently going through the CI testing, but I feel
confident in the fix and explanation. Thanks,
Josef
Josef Bacik (3):
btrfs: wait for block groups to finish caching during allocation
btrfs: move comments to btrfs_loop_type definition
btrfs: cycle through the RAID profiles as a last resort
fs/btrfs/extent-tree.c | 67 ++++++++++++++++++++++++++++++------------
1 file changed, 49 insertions(+), 18 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-20 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 20:12 Josef Bacik [this message]
2023-07-20 20:12 ` [PATCH 1/3] btrfs: wait for block groups to finish caching during allocation Josef Bacik
2023-07-20 22:21 ` Boris Burkov
2023-07-20 20:12 ` [PATCH 2/3] btrfs: move comments to btrfs_loop_type definition Josef Bacik
2023-07-20 22:28 ` Boris Burkov
2023-07-27 16:32 ` David Sterba
2023-07-20 20:12 ` [PATCH 3/3] btrfs: cycle through the RAID profiles as a last resort Josef Bacik
2023-07-20 22:28 ` Boris Burkov
2023-07-21 1:07 ` Josef Bacik
2023-07-25 14:37 ` kernel test robot
2023-07-21 7:36 ` [PATCH 0/3] btrfs: fix generic/475 hang Christoph Hellwig
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.1689883754.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).