From: Christoph Hellwig <hch@infradead.org>
To: ming.lei@redhat.com
Cc: linux-block@vger.kernel.org
Subject: use of the system work queue in ublk
Date: Sun, 17 Jul 2022 23:38:25 -0700 [thread overview]
Message-ID: <YtT/4Y387f/6pxZH@infradead.org> (raw)
Hi Ming,
it seems like ublk uses schedule_work to stop the device, which
includes a del_gendisk. I'm a little fearful this will gets us into
lockdep chains of death once syzbot or Tetsu notice it.
That being said, I don't reall understand the design of
ublk_daemon_monitor_work, which is only used to kick off other
work to start with.
next reply other threads:[~2022-07-18 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 6:38 Christoph Hellwig [this message]
2022-07-18 7:35 ` use of the system work queue in ublk Ming Lei
2022-07-18 8:55 ` Ziyang Zhang
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=YtT/4Y387f/6pxZH@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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.