From: Dipanjan Das <mail.dipanjan.das@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Denis Efremov <efremov@linux.com>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
fleischermarius@googlemail.com, its.priyanka.bose@gmail.com
Subject: Re: INFO: task hung in __floppy_read_block_0
Date: Mon, 1 Aug 2022 22:04:46 -0700 [thread overview]
Message-ID: <CANX2M5YxE31gSU804jm6U4T6uTeCTjgk1gfHM+ockpjHnXfDrw@mail.gmail.com> (raw)
In-Reply-To: <20220731095307.GA12211@1wt.eu>
On Sun, Jul 31, 2022 at 2:53 AM Willy Tarreau <w@1wt.eu> wrote:
>
> Thus I'm a bit confused about what to look for. It's very likely that
> there are still bugs left in this driver, but trying to identify them
> and to validate a fix will be difficult if they cannot be reproduced.
> Maybe they only happen under emulation due to timing issues.
>
> As such, any hint about the exact setup and how long to wait to get
> the error would be much appreciated.
We can confirm that we were able to trigger the issue on the latest
5.19 (commit: 3d7cb6b04c3f3115719235cc6866b10326de34cd) with the
C-repro within a VM. We use this:
https://syzkaller.appspot.com/text?tag=KernelConfig&x=cd73026ceaed1402
config to build the kernel. The issue triggers after around 143
seconds. For all the five times we tried, we were able to reproduce
the issue deterministically every time. Please let us know if you need
any other information.
--
Thanks and Regards,
Dipanjan
next prev parent reply other threads:[~2022-08-02 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 22:00 INFO: task hung in __floppy_read_block_0 Dipanjan Das
2022-07-28 14:23 ` Lukas Bulwahn
2022-07-28 20:20 ` Dipanjan Das
2022-07-29 14:32 ` Lukas Bulwahn
2022-07-31 9:53 ` Willy Tarreau
2022-07-31 10:46 ` Denis Efremov
2022-08-02 5:04 ` Dipanjan Das [this message]
2022-08-02 16:50 ` Willy Tarreau
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=CANX2M5YxE31gSU804jm6U4T6uTeCTjgk1gfHM+ockpjHnXfDrw@mail.gmail.com \
--to=mail.dipanjan.das@gmail.com \
--cc=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=fleischermarius@googlemail.com \
--cc=its.priyanka.bose@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=w@1wt.eu \
/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).