[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94c6680c-1b86-4cee-8e9c-860daf629b59@acm.org>
Date: Wed, 26 Nov 2025 07:48:40 -0800
From: Bart Van Assche <bvanassche@....org>
To: "Rafael J. Wysocki" <rafael@...nel.org>, Yang Yang <yang.yang@...o.com>
Cc: Jens Axboe <axboe@...nel.dk>, Pavel Machek <pavel@...nel.org>,
Len Brown <lenb@...nel.org>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Danilo Krummrich <dakr@...nel.org>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH 0/2] PM: runtime: Fix potential I/O hang
On 11/26/25 3:31 AM, Rafael J. Wysocki wrote:
> Please address the issue differently.
It seems unfortunate to me that __pm_runtime_barrier() can cause
pm_request_resume() to hang. Would it be safe to remove the
cancel_work_sync() call from __pm_runtime_barrier() since
pm_runtime_work() calls functions that check disable_depth
when processing RPM_REQ_SUSPEND and RPM_REQ_AUTOSUSPEND? Would
this be sufficient to fix the reported deadlock?
Thanks,
Bart.
Powered by blists - more mailing lists