[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200917143012.GF38283@mit.edu>
Date: Thu, 17 Sep 2020 10:30:12 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Ming Lei <ming.lei@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-ext4@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-block@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: REGRESSION: 37f4a24c2469: blk-mq: centralise related handling
into blk_mq_get_driver_tag
On Thu, Sep 17, 2020 at 10:20:51AM +0800, Ming Lei wrote:
>
> Obviously there is other more serious issue, since 568f27006577 is
> completely reverted in your test, and you still see list corruption
> issue.
>
> So I'd suggest to find the big issue first. Once it is fixed, maybe
> everything becomes fine.
> ...
> Looks it is more like a memory corruption issue, is there any helpful log
> dumped when running kernel with kasan?
Last night, I ran six VM's using -rc4 with and without KASAN; without
Kasan, half of them hung. With KASAN enabled, all of the test VM's
ran to completion.
This strongly suggests whatever the problem is, it's timing related.
I'll run a larger set of test runs to see if this pattern is confirmed
today.
> BTW, I have kvm/qumu auto test which runs blktest/xfstest over virtio-blk/virito-scsi/loop/nvme
> with xfs/ext4 every two days, and not see such failure recently, but the kernel config is based
> rhel8's config.
Here is the configs I'm using, with and without KASAN. (With KASAN is
enabled is sent as a diff to avoid running into LKML's e-mail size
restrictrions.)
- Ted
View attachment "config" of type "text/plain" (72960 bytes)
View attachment "config.kasan.diff" of type "text/x-diff" (1375 bytes)
Powered by blists - more mailing lists