cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2 hang in xfstests generic/361
Date: Mon, 26 Jul 2021 12:35:34 -0500	[thread overview]
Message-ID: <2c552824-47bd-a757-3314-1d539908815a@redhat.com> (raw)
In-Reply-To: <20210726140058.GA9206@lst.de>

On 7/26/21 9:00 AM, Christoph Hellwig wrote:
> I noticed this hang while testing the iomap_iter series on gfs2,
> but it also reproduces on 5.14-rc3.  This is running locally with
> "-O -p lock_nolock":
> 
(snip)
> generic/361 files ... [ 1479.222703] run fstests generic/361 at 2021-07-26 13:57:10
(snip)
> [ 1491.752587] =============================
> [ 1491.753403] [ BUG: Invalid wait context ]
> [ 1491.754122] 5.14.0-rc2+ #47 Not tainted
> [ 1491.754860] -----------------------------
> [ 1491.755563] kworker/2:1H/1975 is trying to lock:

Hi again Christoph,

Apparently the reason I haven't been seeing this problem myself is
because I've been testing code in an experimental branch in linux-gfs2,
and one of my other patches already fixed the problem. I just pushed my
experimental branch to linux-gfs2/for-next.next4 and the patch that
fixes it is 631e950b2eeb ("gfs2: fix deadlock in gfs2_ail1_empty
withdraw"). Perhaps you can cherry-pick that patch (and others if 
warranted) into your test branch and see if it behaves itself?

Regards,

Bob Peterson



  parent reply	other threads:[~2021-07-26 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 14:00 [Cluster-devel] gfs2 hang in xfstests generic/361 Christoph Hellwig
2021-07-26 14:49 ` Bob Peterson
2021-07-26 17:11 ` Bob Peterson
2021-07-26 17:35 ` Bob Peterson [this message]
2021-07-26 18:50 ` [Cluster-devel] gfs2 hang in xfstests generic/361 (v3) Bob Peterson
2021-07-27  7:05   ` Christoph Hellwig
2021-07-27 14:05     ` Bob Peterson
2021-07-27 14:27       ` Andreas Gruenbacher
2021-07-27 16:41     ` Bob Peterson
2021-07-28  5:39       ` 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=2c552824-47bd-a757-3314-1d539908815a@redhat.com \
    --to=rpeterso@redhat.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 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).