fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Cc: Jan Kara <jack@suse.cz>, fstests <fstests@vger.kernel.org>
Subject: Re: generic/269 hangs on lastest upstream kernel
Date: Tue, 18 Feb 2020 09:35:33 -0500	[thread overview]
Message-ID: <20200218143533.GD12604@mit.edu> (raw)
In-Reply-To: <7adf16bf-d527-1c25-1a24-b4d5e4d757c4@cn.fujitsu.com>

On Tue, Feb 18, 2020 at 11:44:24AM +0800, Yang Xu wrote:
> 
> 
> on 2020/02/14 22:05, Theodore Y. Ts'o wrote:
> > On Fri, Feb 14, 2020 at 09:14:33AM +0800, Yang Xu wrote:
> > > > 
> > > > So were you able to reproduce this on a 5.6.0-rc1 kernel or not?
> > > No. I don't reproduce it on 5.6.0-rc1 kernel, but  5.6.0-rc1 kernel hang on
> > > my KVM machine when run generic/269.
> > 
> > I'm not able to reproduce the 5.6.0-rc1 hang using kvm-xfstests[1].
> > Neither has any other ext4 developers, which is why it might be useful
> > to see if there's something unique in your .config for 5.6.0-rc1.
> > Could you send us the .config you were using?
> > 
> Sorry for the late reply.
> 
> my 5.6.0-rc1 config as attach.

Unfortunately, I just tried using your config with kvm-xfstests, and
it passed without problems.  Did you say this was a reliable
reproducer on your system?

% kvm-xfstests -c 4k generic/269
KERNEL:    kernel 5.6.0-rc2-xfstests #1492 SMP Mon Feb 17 23:22:40 EST 2020 x86_64
CPUS:      2
MEM:       1966.03

ext4/4k: 1 tests, 43 seconds
  generic/269  Pass     42s
Totals: 1 tests, 0 skipped, 0 failures, 0 errors, 42s

FSTESTVER: blktests 9e02419 (Thu, 19 Dec 2019 14:45:55 -0800)
FSTESTVER: e2fsprogs v1.45.4-15-g4b4f7b35 (Wed, 9 Oct 2019 20:25:01 -0400)
FSTESTVER: fio  fio-3.17 (Mon, 16 Dec 2019 15:48:43 -0700)
FSTESTVER: fsverity v1.0 (Wed, 6 Nov 2019 10:35:02 -0800)
FSTESTVER: ima-evm-utils v1.2 (Fri, 26 Jul 2019 07:42:17 -0400)
FSTESTVER: nvme-cli v1.9-159-g18119bc (Thu, 26 Dec 2019 11:04:01 -0700)
FSTESTVER: quota  9a001cc (Tue, 5 Nov 2019 16:12:59 +0100)
FSTESTVER: util-linux v2.35-19-g95afec771 (Fri, 24 Jan 2020 12:25:35 -0500)
FSTESTVER: xfsprogs v5.4.0 (Fri, 20 Dec 2019 16:47:12 -0500)
FSTESTVER: xfstests linux-v3.8-2652-g002e349c (Fri, 24 Jan 2020 00:49:40 -0500)
FSTESTVER: xfstests-bld 6f10355 (Fri, 24 Jan 2020 12:36:30 -0500)
FSTESTCFG: 4k
FSTESTSET: generic/269
FSTESTOPT: aex

This was run on a Debian testing system, with kvm version:

QEMU emulator version 4.2.0 (Debian 1:4.2-3)

What about hardware details of your system?  How many CPU's, memory,
etc.?  And what sort of storage device are you using for kvm?  (I'm
using virtio-scsi backed by LVM volumes for the scratch and test
partitions.)

						- Ted

  parent reply	other threads:[~2020-02-18 14:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  8:14 generic/269 hangs on lastest upstream kernel Yang Xu
2020-02-12 10:54 ` Jan Kara
2020-02-13  8:49   ` Yang Xu
2020-02-13 17:08     ` Theodore Y. Ts'o
2020-02-14  1:14       ` Yang Xu
2020-02-14 14:05         ` Theodore Y. Ts'o
     [not found]           ` <7adf16bf-d527-1c25-1a24-b4d5e4d757c4@cn.fujitsu.com>
2020-02-18 14:35             ` Theodore Y. Ts'o [this message]
2020-02-19 10:57               ` Yang Xu
2020-02-13 21:10     ` Jan Kara
     [not found]       ` <062ac52c-3a16-22ef-6396-53334ed94783@cn.fujitsu.com>
2020-02-14 15:00         ` Jan Kara
2020-02-18  3:25           ` Yang Xu
2020-02-18  8:24             ` Jan Kara
2020-02-18  9:46               ` Yang Xu
2020-02-18 11:03                 ` Jan Kara
2020-02-19 10:09                   ` Yang Xu
     [not found]                     ` <73af3d5c-ca64-3ad3-aee2-1e78ee4fae4a@cn.fujitsu.com>
2020-02-19 12:43                       ` Jan Kara
2020-02-19 15:20                         ` Theodore Y. Ts'o
2020-02-20  1:35                           ` Yang Xu
2020-02-25  6:03                             ` Yang Xu

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=20200218143533.GD12604@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=xuyang2018.jy@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 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).