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: Fri, 14 Feb 2020 09:05:41 -0500 [thread overview]
Message-ID: <20200214140541.GA434121@mit.edu> (raw)
In-Reply-To: <1c81c16b-6e31-74cb-0b88-46663fad500d@cn.fujitsu.com>
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?
[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-xfstests.md
Cheers,
- Ted
next prev parent reply other threads:[~2020-02-14 14:05 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 [this message]
[not found] ` <7adf16bf-d527-1c25-1a24-b4d5e4d757c4@cn.fujitsu.com>
2020-02-18 14:35 ` Theodore Y. Ts'o
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=20200214140541.GA434121@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 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.