All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: Test scrub and replace race for RAID56
Date: Sat, 24 Dec 2016 17:45:25 +0800	[thread overview]
Message-ID: <20161224094525.GR1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20161222020251.12272-1-quwenruo@cn.fujitsu.com>

On Thu, Dec 22, 2016 at 10:02:51AM +0800, Qu Wenruo wrote:
> Although by design, btrfs scrub and replace share the same code path, so
> they are exclusive to each other.
> 
> But the fact is, there is still some critical region not protected well,
> so we can have the following kernel panic, especially easy to trigger on
> RAID5/6 profiles.

Could btrfs/069 reproduce the panic? It also races scrub and replace,
but with fsstress running in background, raid5/6 profiles are part of
the default test configs.

Also, is there a known fix available in Linus tree or btrfs tree? If
not, I'd push this new test after there's a known fix (if it's worth a
new test).

Thanks,
Eryu

  reply	other threads:[~2016-12-24  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22  2:02 [PATCH] fstests: btrfs: Test scrub and replace race for RAID56 Qu Wenruo
2016-12-24  9:45 ` Eryu Guan [this message]
2016-12-26  0:23   ` Qu Wenruo

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=20161224094525.GR1859@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    /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.