All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Zorro Lang <zlang@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [Bug report] fstests generic/051 (on xfs) hang on latest linux v6.5-rc5+
Date: Sun, 11 Jun 2023 18:51:45 -0700	[thread overview]
Message-ID: <20230612015145.GA11441@frogsfrogsfrogs> (raw)
In-Reply-To: <ZIZSPyzReZkGBEFy@dread.disaster.area>

On Mon, Jun 12, 2023 at 09:01:19AM +1000, Dave Chinner wrote:
> On Sun, Jun 11, 2023 at 08:48:36PM +0800, Zorro Lang wrote:
> > Hi,
> > 
> > When I tried to do fstests regression test this weekend on latest linux
> > v6.5-rc5+ (HEAD=64569520920a3ca5d456ddd9f4f95fc6ea9b8b45), nearly all
> > testing jobs on xfs hang on generic/051 (more than 24 hours, still blocked).
> > No matter 1k or 4k blocksize, general disk or pmem dev, or any architectures,
> > or any mkfs/mount options testing, all hang there.
> 
> Yup, I started seeing this on upgrade to 6.5-rc5, too. xfs/079
> generates it, because the fsstress process is crashing when the
> XFS filesystems shuts down (maybe a SIGBUS from a mmap page fault?)
> I don't know how reproducable it is yet; these only showed up in my
> thrusday night testing so I haven't had a chance to triage it yet.
> 
> > Someone console log as below (a bit long), the call trace doesn't contains any
> > xfs functions, it might be not a xfs bug, but it can't be reproduced on ext4.
> 
> AFAICT, the coredump is being done on the root drive (where fsstress
> is being executed from), not the XFS test/scratch devices that
> fsstress processes are exercising. I have ext3 root drives for my
> test machines, so at this point I'm not sure that this is even a
> filesystem related regression. i.e. it may be a recent regression in
> the coredump or signal handling code....

Willy was complaining about the same thing on Friday.  Oddly I've not
seen any problems with coredumps on 6.4-rc5, so .... <shrug>

--D

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

  reply	other threads:[~2023-06-12  1:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 12:48 [Bug report] fstests generic/051 (on xfs) hang on latest linux v6.5-rc5+ Zorro Lang
2023-06-11 13:40 ` Zorro Lang
2023-06-11 23:01 ` Dave Chinner
2023-06-12  1:51   ` Darrick J. Wong [this message]
2023-06-12  2:21     ` [6.5-rc5 regression] core dump hangs (was Re: [Bug report] fstests generic/051 (on xfs) hang on latest linux v6.5-rc5+) Dave Chinner
2023-06-12  3:14       ` Linus Torvalds
2023-06-12  5:16         ` Dave Chinner
2023-06-12  5:34           ` Linus Torvalds
2023-06-12  5:49             ` Dave Chinner
2023-06-12  6:11               ` Linus Torvalds
2023-06-12  8:45                 ` Eric W. Biederman
2023-06-12  9:30                   ` Zorro Lang
2023-06-12 11:27                   ` Dave Chinner
2023-06-12  6:36         ` Zorro Lang
2023-06-12 15:36         ` Darrick J. Wong
2023-06-12 15:52           ` Eric W. Biederman
2023-06-12 15:56           ` Linus Torvalds
2023-06-12 16:27             ` Jens Axboe
2023-06-12 16:38               ` Jens Axboe
2023-06-12 16:42                 ` Linus Torvalds
2023-06-12 16:45                   ` Jens Axboe
2023-06-12 16:57                     ` Linus Torvalds
2023-06-12 17:11                       ` Eric W. Biederman
2023-06-12 17:30                         ` Jens Axboe
2023-06-12 17:29                       ` Jens Axboe
2023-06-12 17:51                         ` Linus Torvalds
2023-06-12 17:53                           ` Jens Axboe
2023-06-12 17:56                             ` Linus Torvalds
2023-06-12 18:34                           ` Linus Torvalds
2023-06-12 23:33                             ` Dave Chinner
2023-06-12 16:45                   ` Linus Torvalds

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=20230612015145.GA11441@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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 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.