All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, leah.rumancik@gmail.com
Subject: Re: soft lockup in xfs/170 on a file system formatted with -m crc=0
Date: Sat, 6 Nov 2021 10:52:09 -0400	[thread overview]
Message-ID: <YYaWma0v5qrECIts@mit.edu> (raw)
In-Reply-To: <20211106021031.GV24307@magnolia>

On Fri, Nov 05, 2021 at 07:10:31PM -0700, Darrick J. Wong wrote:
> On Fri, Nov 05, 2021 at 01:25:05PM -0400, Theodore Ts'o wrote:
> > Is this a known failure?  I can reliably reproduce this soft lockup
> > running xfs/170 using "gce-xfstests -c xfs/v4 xfs/170" using
> > v5.15-rc4.  The xfs/v4 test config formats the file system using -m
> > crc=0 with no special mount options.
> > 
> > I've attached the kernel config that I used; it's the standard one
> > obtained via "gce-xfstests install-kconfig"[1].
> 
> Also, uh... 5.15 didn't prove to be a stable testing base (at least not
> without a bunch of other patches to kvm, the memory manager, and the
> block layer) until 5.15-rc7.

Thanks, I haven't had a problem using 5.15-rc4 as a testing base for
ext4, so I wasn't aware of that.  I just tested xfs/170 on 5.15 final,
and it is no longer triggering a soft lockup.

Thanks again,

					- Ted

      reply	other threads:[~2021-11-06 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 17:25 soft lockup in xfs/170 on a file system formatted with -m crc=0 Theodore Ts'o
2021-11-06  1:58 ` xfs/076 takes a long long time testing with a realtime volume Theodore Ts'o
2021-11-06  2:08   ` Darrick J. Wong
2021-11-06 16:43     ` Theodore Ts'o
2021-11-06  2:10 ` soft lockup in xfs/170 on a file system formatted with -m crc=0 Darrick J. Wong
2021-11-06 14:52   ` Theodore Ts'o [this message]

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=YYaWma0v5qrECIts@mit.edu \
    --to=tytso@mit.edu \
    --cc=djwong@kernel.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-xfs@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.