From: Bart Van Assche <bvanassche@acm.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Yang Yang <yang.yang@vivo.com>
Cc: Jens Axboe <axboe@kernel.dk>, Pavel Machek <pavel@kernel.org>,
Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/2] PM: runtime: Fix potential I/O hang
Date: Wed, 26 Nov 2025 07:48:40 -0800 [thread overview]
Message-ID: <94c6680c-1b86-4cee-8e9c-860daf629b59@acm.org> (raw)
In-Reply-To: <CAJZ5v0jsdsyVd3hPWni1Vj+daQS8PdWJCjboJHHHbBjBMeSxzg@mail.gmail.com>
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.
next prev parent reply other threads:[~2025-11-26 15:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:16 [PATCH 0/2] PM: runtime: Fix potential I/O hang Yang Yang
2025-11-26 10:16 ` [PATCH 1/2] PM: runtime: Fix I/O hang due to race between resume and runtime disable Yang Yang
2025-11-26 11:30 ` Rafael J. Wysocki
2025-11-26 11:59 ` YangYang
2025-11-26 12:36 ` Rafael J. Wysocki
2025-11-26 15:33 ` Bart Van Assche
2025-11-26 15:41 ` Rafael J. Wysocki
2025-11-26 18:40 ` Bart Van Assche
2025-11-27 11:29 ` YangYang
2025-11-27 12:44 ` Rafael J. Wysocki
2025-11-28 7:20 ` YangYang
2025-12-01 16:40 ` Bart Van Assche
2025-11-26 18:06 ` Bart Van Assche
2025-11-26 19:16 ` Rafael J. Wysocki
2025-11-26 19:34 ` Rafael J. Wysocki
2025-11-26 20:17 ` Rafael J. Wysocki
2025-11-26 21:10 ` Bart Van Assche
2025-11-26 21:30 ` Rafael J. Wysocki
2025-11-26 22:47 ` Bart Van Assche
2025-11-27 12:34 ` Rafael J. Wysocki
2025-12-01 9:46 ` YangYang
2025-12-01 12:56 ` YangYang
2025-12-01 18:55 ` Rafael J. Wysocki
2025-12-02 10:33 ` YangYang
2025-12-02 12:18 ` Rafael J. Wysocki
2025-12-01 18:47 ` Rafael J. Wysocki
2025-12-01 19:58 ` [PATCH v1] PM: sleep: Do not flag runtime PM workqueue as freezable Rafael J. Wysocki
2025-12-02 1:06 ` Bart Van Assche
2025-12-02 11:53 ` Rafael J. Wysocki
2025-12-02 13:29 ` Rafael J. Wysocki
2025-12-02 10:36 ` YangYang
2025-12-02 14:58 ` Ulf Hansson
2025-12-02 0:40 ` [PATCH 1/2] PM: runtime: Fix I/O hang due to race between resume and runtime disable Bart Van Assche
2025-12-02 12:14 ` Rafael J. Wysocki
2025-12-02 13:37 ` Rafael J. Wysocki
2025-12-05 15:24 ` [PATCH v2] PM: sleep: Do not flag runtime PM workqueue as freezable Rafael J. Wysocki
2025-12-05 19:10 ` Bart Van Assche
2025-12-07 11:23 ` Rafael J. Wysocki
2025-11-26 10:16 ` [PATCH 2/2] blk-mq: Fix I/O hang caused by incomplete device resume Yang Yang
2025-11-26 11:31 ` [PATCH 0/2] PM: runtime: Fix potential I/O hang Rafael J. Wysocki
2025-11-26 15:48 ` Bart Van Assche [this message]
2025-11-26 16:59 ` Rafael J. Wysocki
2025-11-26 17:21 ` Rafael J. Wysocki
2025-11-26 17:34 ` 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=94c6680c-1b86-4cee-8e9c-860daf629b59@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=yang.yang@vivo.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