From: Tarun Sahu <tarunsahu@google.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: bvanassche@acm.org, john.g.garry@oracle.com, mlombard@redhat.com,
loberman@redhat.com, mclapinski@google.com, dmatlack@google.com,
driver-core@lists.linux.dev, linux-pci@vger.kernel.org,
Pasha Tatashin <pasha.tatashin@soleen.com>,
jordanrichards@google.com, souravsgl@google.com,
stuart.w.hayes@gmail.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, emilne@redhat.com,
jmeneghi@redhat.com, linux-scsi@vger.kernel.org,
Tarun Sahu <tarunsahu@google.com>,
David Jeffery <djeffery@redhat.com>
Subject: [PATCH v19 2/7] driver core: Prevent device_add() during system shutdown
Date: Thu, 16 Jul 2026 23:04:06 +0000 [thread overview]
Message-ID: <20260716230411.2767394-3-tarunsahu@google.com> (raw)
In-Reply-To: <20260716230411.2767394-1-tarunsahu@google.com>
In Async device shutdown, device_kset->list lock is released to handle
asynchronisation and hold again to get entry from device_kset->list.
Which will leave window when device_add can try to add the device to
device_kset list and temper with ongoing shutdown process. New added
device can be async type or sync type and might also introduce new
dependency which can cause device_shutdown path to deadlock. S is
waiting C to finish but C is never scheduled as it was added recently
from device_add path. And C can only be scheduled when main loops
continue to reach to C which is waiting on S.
So, When a system enters shutdown (SYSTEM_HALT, SYSTEM_POWER_OFF, or
SYSTEM_RESTART), new devices should not be allowed to be added.
Adding system_state check (system_is_shutting_down()) to avoid
device_add incase of these states of the system.
While device_add() performs an initial check of system_is_shutting_down(),
a race window exists between this initial check and kobject_add(),
during which device_shutdown() may already be scanning devices_kset->list.
If device_shutdown() passes the device after kobject_add() registers it
onto devices_kset->list, device_add() would otherwise complete device
initialization and driver matching, leaving an active device running
after system shutdown finishes.
Fix this TOCTOU race by re-checking system_is_shutting_down() under
devices_kset->list_lock right after kobject_add().
Signed-off-by: Tarun Sahu <tarunsahu@google.com>
Signed-off-by: David Jeffery <djeffery@redhat.com>
---
drivers/base/core.c | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 76ba02c26aa5..78b90326addb 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -47,6 +47,22 @@ static bool fw_devlink_drv_reg_done;
static bool fw_devlink_best_effort;
static struct workqueue_struct *device_link_wq;
+/**
+ * system_is_shutting_down - Check if system state is not active.
+ *
+ * When system state is not active and in shutdown state, new devices
+ * should not be allowed to be added.
+ *
+ * If system_state is SYSTEM_HALT || SYSTEM_POWER_OFF || SYSTEM_RESTART
+ * this function will return true.
+ */
+static inline bool system_is_shutting_down(void)
+{
+ return system_state == SYSTEM_HALT ||
+ system_state == SYSTEM_POWER_OFF ||
+ system_state == SYSTEM_RESTART;
+}
+
/**
* __fwnode_link_add - Create a link between two fwnode_handles.
* @con: Consumer end of the link.
@@ -3650,6 +3666,11 @@ int device_add(struct device *dev)
if (!dev)
goto done;
+ if (unlikely(system_is_shutting_down())) {
+ error = -ESHUTDOWN;
+ goto done;
+ }
+
if (!dev->p) {
error = device_private_init(dev);
if (error)
@@ -3699,6 +3720,18 @@ int device_add(struct device *dev)
goto Error;
}
+ /*
+ * Check system_state again under list_lock to prevent a TOCTOU race
+ * where device_shutdown() runs concurrently and misses this device.
+ */
+ spin_lock(&devices_kset->list_lock);
+ if (unlikely(system_is_shutting_down())) {
+ spin_unlock(&devices_kset->list_lock);
+ error = -ESHUTDOWN;
+ goto ShutdownError;
+ }
+ spin_unlock(&devices_kset->list_lock);
+
/* notify platform of device entry */
device_platform_notify(dev);
@@ -3818,6 +3851,7 @@ int device_add(struct device *dev)
attrError:
device_platform_notify_remove(dev);
kobject_uevent(&dev->kobj, KOBJ_REMOVE);
+ ShutdownError:
glue_dir = get_glue_dir(dev);
kobject_del(&dev->kobj);
Error:
--
2.55.0.229.g6434b31f56-goog
next prev parent reply other threads:[~2026-07-17 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 23:04 [PATCH v19 0/7] shut down devices asynchronously Tarun Sahu
2026-07-16 23:04 ` [PATCH v19 1/7] device_core: rely on put_device to free dev->p Tarun Sahu
2026-07-16 23:04 ` Tarun Sahu [this message]
2026-07-16 23:04 ` [PATCH v19 3/7] driver core: separate function to shutdown one device Tarun Sahu
2026-07-16 23:04 ` [PATCH v19 4/7] driver core: do not always lock parent in shutdown Tarun Sahu
2026-07-16 23:04 ` [PATCH v19 5/7] driver core: async device shutdown infrastructure Tarun Sahu
2026-07-16 23:04 ` [PATCH v19 6/7] PCI: Enable async shutdown support Tarun Sahu
2026-07-16 23:04 ` [PATCH v19 7/7] scsi: " Tarun Sahu
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=20260716230411.2767394-3-tarunsahu@google.com \
--to=tarunsahu@google.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bhelgaas@google.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=djeffery@redhat.com \
--cc=dmatlack@google.com \
--cc=driver-core@lists.linux.dev \
--cc=emilne@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmeneghi@redhat.com \
--cc=john.g.garry@oracle.com \
--cc=jordanrichards@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=mclapinski@google.com \
--cc=mlombard@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=rafael@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=souravsgl@google.com \
--cc=stuart.w.hayes@gmail.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