From: bvanassche@acm.org (Bart Van Assche)
Subject: v5.1-rc1: New NVMe warning triggered by nvme_delete_ctrl_work()
Date: Mon, 11 Mar 2019 15:43:46 -0700 [thread overview]
Message-ID: <1552344226.45180.104.camel@acm.org> (raw)
Hello,
If I run the nvme tests from blktests against Linus' current master then
the following warning appears:
WARNING: CPU: 5 PID: 98 at kernel/workqueue.c:3030 __flush_work+0x423/0x430
CPU: 5 PID: 98 Comm: kworker/u12:2 Not tainted 5.0.0-dbg+ #1
Workqueue: nvme-delete-wq nvme_delete_ctrl_work
RIP: 0010:__flush_work+0x423/0x430
Call Trace:
__cancel_work_timer+0x200/0x2b0
cancel_work_sync+0x10/0x20
nvmet_ctrl_free+0x217/0x330 [nvmet]
nvmet_sq_destroy+0xc1/0x290 [nvmet]
nvme_loop_destroy_admin_queue+0x29/0x50 [nvme_loop]
nvme_loop_shutdown_ctrl+0xb2/0xd0 [nvme_loop]
nvme_loop_delete_ctrl_host+0x15/0x20 [nvme_loop]
nvme_do_delete_ctrl+0x97/0xcd
nvme_delete_ctrl_work+0x15/0x17
process_one_work+0x4f1/0xa40
worker_thread+0x67/0x5b0
kthread+0x1cf/0x1f0
ret_from_fork+0x24/0x30
I think this is a result of commit 4d43d395fed1 ("workqueue: Try to
catch flush_work() without INIT_WORK()").
Bart.
next reply other threads:[~2019-03-11 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 22:43 Bart Van Assche [this message]
2019-03-12 1:50 ` v5.1-rc1: New NVMe warning triggered by nvme_delete_ctrl_work() yuyufen
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=1552344226.45180.104.camel@acm.org \
--to=bvanassche@acm.org \
/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