From: <ed.tsai@mediatek.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <chun-hung.wu@mediatek.com>,
<freddy.shin@mediatek.com>, Ed Tsai <ed.tsai@mediatek.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
<linux-pm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 1/1] PM: runtime: fix bitfield race of needs_force_resume
Date: Mon, 15 Dec 2025 20:21:42 +0800 [thread overview]
Message-ID: <20251215122154.3180001-1-ed.tsai@mediatek.com> (raw)
From: Ed Tsai <ed.tsai@mediatek.com>
needs_force_resume is a bitfield member in struct dev_pm_info and must
be accessed under the same lock as its bitfield group.
A real concurrent write was observed between needs_force_resume and
idle_notification; stacks below:
write needs_force_resume:
pm_runtime_reinit+0x110/0x360
really_probe+0xe0/0x464
__driver_probe_device+0x9c/0x104
driver_probe_device+0x3c/0x1a8
__device_attach_driver+0x100/0x17c
bus_for_each_drv+0x10c/0x168
__device_attach_async_helper+0x7c/0xf4
async_run_entry_fn+0x4c/0x1b4
process_scheduled_works+0x1dc/0x498
worker_thread+0x220/0x320
kthread+0x150/0x27c
ret_from_fork+0x10/0x20
write idle_notification:
rpm_idle+0x464/0x5f8
__pm_runtime_idle+0x7c/0x170
scsi_autopm_put_device+0x18/0x28
scsi_sysfs_add_sdev+0x1a0/0x1d8
scsi_probe_and_add_lun+0xbd8/0xcd0
__scsi_add_device+0xb8/0x11c
ufshcd_async_scan+0xb4/0x3a4
async_run_entry_fn+0x4c/0x1b4
process_scheduled_works+0x1dc/0x498
worker_thread+0x220/0x320
kthread+0x150/0x27c
ret_from_fork+0x10/0x20
Fixes: 89d9cec3b1e9 ("PM: runtime: Clear power.needs_force_resume in pm_runtime_reinit()")
Signed-off-by: Ed Tsai <ed.tsai@mediatek.com>
---
drivers/base/power/runtime.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c
index 84676cc24221..3328543b1ed8 100644
--- a/drivers/base/power/runtime.c
+++ b/drivers/base/power/runtime.c
@@ -1879,11 +1879,22 @@ void pm_runtime_reinit(struct device *dev)
pm_runtime_put(dev->parent);
}
}
+
/*
* Clear power.needs_force_resume in case it has been set by
* pm_runtime_force_suspend() invoked from a driver remove callback.
*/
+ if (dev->power.irq_safe)
+ spin_lock(&dev->power.lock);
+ else
+ spin_lock_irq(&dev->power.lock);
+
dev->power.needs_force_resume = false;
+
+ if (dev->power.irq_safe)
+ spin_unlock(&dev->power.lock);
+ else
+ spin_unlock_irq(&dev->power.lock);
}
/**
--
2.45.2
next reply other threads:[~2025-12-15 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 12:21 ed.tsai [this message]
2025-12-15 14:21 ` [PATCH v1] PM: runtime: Do not clear needs_force_resume with enabled runtime PM Rafael J. Wysocki
2025-12-15 15:48 ` Ulf Hansson
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=20251215122154.3180001-1-ed.tsai@mediatek.com \
--to=ed.tsai@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chun-hung.wu@mediatek.com \
--cc=dakr@kernel.org \
--cc=freddy.shin@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®