From: Christoph Hellwig <hch@infradead.org>
To: "Dae R. Jeong" <threeearcat@gmail.com>
Cc: axboe@kernel.dk, rostedt@goodmis.org, mingo@redhat.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: INFO: task hung in blk_trace_remove
Date: Sun, 3 Jul 2022 00:12:19 -0700 [thread overview]
Message-ID: <YsFBU1ZzeTy1lVu4@infradead.org> (raw)
In-Reply-To: <YsEhsEvhZyoJFtSO@archdragon>
On Sun, Jul 03, 2022 at 01:57:20PM +0900, Dae R. Jeong wrote:
> Hello,
>
> We observed an issue "INFO: task hung in blk_trace_remove" during
> fuzzing.
>
> Unfortunately, we have not found a reproducer for the crash yet. We
> will inform you if we have any update on this crash.
>
> The crash information is attached at the end of this email.
This looks like it is due to locking an on the /dev/sg node instead
of the more usual (and more tested) block device node.
It might make sense to run with lockdep enabled to get a better
grip on potential locking issues here.
next prev parent reply other threads:[~2022-07-03 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 4:57 INFO: task hung in blk_trace_remove Dae R. Jeong
2022-07-03 5:05 ` Dae R. Jeong
2022-07-03 7:12 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-21 7:12 syzbot
2020-03-21 7:15 ` Dmitry Vyukov
2020-03-23 17:12 ` Todd Kjos
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=YsFBU1ZzeTy1lVu4@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=threeearcat@gmail.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