From: Jens Axboe <axboe@kernel.dk>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: Pavel Machek <pavel@ucw.cz>, Jan Kara <jack@suse.cz>,
Tejun Heo <tj@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
AceLan Kao <acelan.kao@canonical.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] bdi: Do not use freezable workqueue
Date: Fri, 4 Oct 2019 07:22:25 -0600 [thread overview]
Message-ID: <0002b2f3-d17c-0d49-52f4-b2ce31832e6c@kernel.dk> (raw)
In-Reply-To: <20191004100025.70798-1-mika.westerberg@linux.intel.com>
On 10/4/19 4:00 AM, Mika Westerberg wrote:
> A removable block device, such as NVMe or SSD connected over Thunderbolt
> can be hot-removed any time including when the system is suspended. When
> device is hot-removed during suspend and the system gets resumed, kernel
> first resumes devices and then thaws the userspace including freezable
> workqueues. What happens in that case is that the NVMe driver notices
> that the device is unplugged and removes it from the system. This ends
> up calling bdi_unregister() for the gendisk which then schedules
> wb_workfn() to be run one more time.
>
> However, since the bdi_wq is still frozen flush_delayed_work() call in
> wb_shutdown() blocks forever halting system resume process. User sees
> this as hang as nothing is happening anymore.
>
> Triggering sysrq-w reveals this:
>
> Workqueue: nvme-wq nvme_remove_dead_ctrl_work [nvme]
> Call Trace:
> ? __schedule+0x2c5/0x630
> ? wait_for_completion+0xa4/0x120
> schedule+0x3e/0xc0
> schedule_timeout+0x1c9/0x320
> ? resched_curr+0x1f/0xd0
> ? wait_for_completion+0xa4/0x120
> wait_for_completion+0xc3/0x120
> ? wake_up_q+0x60/0x60
> __flush_work+0x131/0x1e0
> ? flush_workqueue_prep_pwqs+0x130/0x130
> bdi_unregister+0xb9/0x130
> del_gendisk+0x2d2/0x2e0
> nvme_ns_remove+0xed/0x110 [nvme_core]
> nvme_remove_namespaces+0x96/0xd0 [nvme_core]
> nvme_remove+0x5b/0x160 [nvme]
> pci_device_remove+0x36/0x90
> device_release_driver_internal+0xdf/0x1c0
> nvme_remove_dead_ctrl_work+0x14/0x30 [nvme]
> process_one_work+0x1c2/0x3f0
> worker_thread+0x48/0x3e0
> kthread+0x100/0x140
> ? current_work+0x30/0x30
> ? kthread_park+0x80/0x80
> ret_from_fork+0x35/0x40
>
> This is not limited to NVMes so exactly same issue can be reproduced by
> hot-removing SSD (over Thunderbolt) while the system is suspended.
>
> Prevent this from happening by removing WQ_FREEZABLE from bdi_wq.
This series looks good for me, I don't think there's a reason for
the workers to be marked freezable.
--
Jens Axboe
next prev parent reply other threads:[~2019-10-04 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 10:00 Mika Westerberg
2019-10-04 10:00 ` [PATCH 2/2] Revert "libata, freezer: avoid block device removal while system is frozen" Mika Westerberg
2019-10-04 13:22 ` Jens Axboe [this message]
2019-10-06 15:08 ` [PATCH 1/2] bdi: Do not use freezable workqueue Rafael J. Wysocki
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=0002b2f3-d17c-0d49-52f4-b2ce31832e6c@kernel.dk \
--to=axboe@kernel.dk \
--cc=acelan.kao@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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
Powered by JetHome