From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-dy1-f182.google.com (mail-dy1-f182.google.com [74.125.82.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A39C63E3C4E for ; Mon, 27 Apr 2026 17:17:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.82.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777310235; cv=none; b=ldvapAcd1fOkyZNAH5eJ5Ymm6mekMb6Jc8CL4tdwbuLYmLH5FEwZgwIwJbSODlTEwQK+LYhVovSR1lgK+WsafRGG7WciFdKuiJn891OAfJBXLOiXWOImiy4o4tU2Db6En7yHBQ/BUFHYRu76T9y5z9I1L4Ax0tpCzoU63NTTY7k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777310235; c=relaxed/simple; bh=5iofg6BiBerw4YzLBYZg1crYwJrVbXaLylHryjB9P2M=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=GXuC4byaSb/dUalUuBszVs0mt7Vuut8UgQBaNRycd50Lkldd4uoduXYS2eCPbkS+LbO7pYL16jYx8yBHdNOyb3FhtIUc8be0Sf+l0hwabT8EwQr4WmOKWUHhtg9agJKdtTiUBFRUD33mDPDRsQcJtTkpy94ZwYkWSvpSDe9rG2k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b=DzuisDdp; arc=none smtp.client-ip=74.125.82.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="DzuisDdp" Received: by mail-dy1-f182.google.com with SMTP id 5a478bee46e88-2d891442388so19240076eec.0 for ; Mon, 27 Apr 2026 10:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1777310232; x=1777915032; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=1/dyHluDEdWWUMrNbZvpFAaF6IyD8Biihb2PWsOxHWs=; b=DzuisDdpBTjiX3haYe5G+FctHNW4ZMZI+4+Xa+gAktstVCSdt39K8IV5WOizp85PE8 xeQ7M0OTpsgspiIzsrbVVIUSp5FSuNJEFOszy+z3qg8kDA+AIitC74io5o3jdhKXhM0Z MAvJLYV10hhfJEt2kDMh2ShsfZZnVaMEJpvA4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777310232; x=1777915032; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=1/dyHluDEdWWUMrNbZvpFAaF6IyD8Biihb2PWsOxHWs=; b=DjbgJJwkcj2Xk5Ia/3PJ/CujloB09WCqJoktKFLl43TpiK4XBbWXxBUjEvU2hEsxBR rhmoXL8d7931Pmm8AuYXr3dT6VSfTRYMbGyJ9w+WeD1/x2L67Fm6SoHat6VpXjRpH9C3 ReHP9vN+bMyVUGIeAgFwxlpoeW5bQDkMbBDeRgq8gp4lXmnFrvQYDs8PmTLmhTwrjPwr D3wZGALSROncoikpubqnGiMjhzPiTPqzx//A6vysUWsiGrJCScm5dXbGMrhDFXk7Z1DL O1RE+4TR1cQH9jgZLc8meaB+lZIFDj8wL4Bk5j1mt1x5bc/tP6h7O2pSG18EPkrgMFTJ sg4Q== X-Gm-Message-State: AOJu0YyzsoOHgDXz/K639r16lAM8UPigFKBzDOiHvotxWAKSpNqWDhlz WeFlFtECr7QXONB4LZIrQfG9IziGgs9F6apC2fVllRuVFr6W+QHN+c9guVRTG8+QRhPwzqEt1Y6 zVmg= X-Gm-Gg: AeBDiesgQPsg4CFVXOASAvmeJ7vOWgiYMcnpLxQnDB6hQkvO8ZWho56861OSVx14c0i rc05WJQcYvCaMVjootpcXLYugmniQlXg/Z0s0Wgib+LpTXpu1d+p9JH6PMw1jtK1LRHrAF+Ase1 HNxc/Yhn2c/ANd8OwDC63oQ3zY8rdD5qt4XxiGeLTB/S8L0q+Oy+T3f+xPG2f4ahXS6jOcoBylZ IXJN5hs5+p1gr7nS3MU6cAIiSnKoGBqm5S+7Vd71zC8nabuBDLtET2ILsr7CwIujtRUqSvKQN1X n4GsV/VWjiAYI+GA5vCvWrVPHYu+s22PgqSIDmd86f2qOlGP4+5det77dT2gK3xBdFcx2e9JLzP lJ+9JdOGPNKM9JfclzUsots83Yf8SIeW8k2wvpTF7SQa07a2ScLPRbibsuSrFkoXuOp68TAZrkt QSsXzKblGk4tHfQbcrMDlIPeXO194eVDepyMLkVLqiK1zbdeSHfiWEYst5aP6wzizO7DfzCXY7F 2RXRiUZJne/S6KRLC1cbw== X-Received: by 2002:a05:7301:1291:b0:2ea:5057:a333 with SMTP id 5a478bee46e88-2ea5057b8dfmr16811433eec.15.1777310231759; Mon, 27 Apr 2026 10:17:11 -0700 (PDT) Received: from dianders.sjc.corp.google.com ([2a00:79e0:2e7c:8:389e:b840:2892:97c2]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-2e53a4a7ff1sm43990493eec.9.2026.04.27.10.17.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Apr 2026 10:17:11 -0700 (PDT) From: Douglas Anderson To: stable@vger.kernel.org Cc: Douglas Anderson , Alan Stern , "Rafael J. Wysocki (Intel)" , Danilo Krummrich , Greg Kroah-Hartman , Marek Szyprowski Subject: [PATCH 6.1.y] driver core: Don't let a device probe until it's ready Date: Mon, 27 Apr 2026 10:17:02 -0700 Message-ID: <20260427171702.496719-1-dianders@chromium.org> X-Mailer: git-send-email 2.54.0.545.g6539524ca2-goog In-Reply-To: <2026042756-vendor-speed-aac0@gregkh> References: <2026042756-vendor-speed-aac0@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit The moment we link a "struct device" into the list of devices for the bus, it's possible probe can happen. This is because another thread can load the driver at any time and that can cause the device to probe. This has been seen in practice with a stack crawl that looks like this [1]: really_probe() __driver_probe_device() driver_probe_device() __driver_attach() bus_for_each_dev() driver_attach() bus_add_driver() driver_register() __platform_driver_register() init_module() [some module] do_one_initcall() do_init_module() load_module() __arm64_sys_finit_module() invoke_syscall() As a result of the above, it was seen that device_links_driver_bound() could be called for the device before "dev->fwnode->dev" was assigned. This prevented __fw_devlink_pickup_dangling_consumers() from being called which meant that other devices waiting on our driver's sub-nodes were stuck deferring forever. It's believed that this problem is showing up suddenly for two reasons: 1. Android has recently (last ~1 year) implemented an optimization to the order it loads modules [2]. When devices opt-in to this faster loading, modules are loaded one-after-the-other very quickly. This is unlike how other distributions do it. The reproduction of this problem has only been seen on devices that opt-in to Android's "parallel module loading". 2. Android devices typically opt-in to fw_devlink, and the most noticeable issue is the NULL "dev->fwnode->dev" in device_links_driver_bound(). fw_devlink is somewhat new code and also not in use by all Linux devices. Even though the specific symptom where "dev->fwnode->dev" wasn't assigned could be fixed by moving that assignment higher in device_add(), other parts of device_add() (like the call to device_pm_add()) are also important to run before probe. Only moving the "dev->fwnode->dev" assignment would likely fix the current symptoms but lead to difficult-to-debug problems in the future. Fix the problem by preventing probe until device_add() has run far enough that the device is ready to probe. If somehow we end up trying to probe before we're allowed, __driver_probe_device() will return -EPROBE_DEFER which will make certain the device is noticed. In the race condition that was seen with Android's faster module loading, we will temporarily add the device to the deferred list and then take it off immediately when device_add() probes the device. Instead of adding another flag to the bitfields already in "struct device", instead add a new "flags" field and use that. This allows us to freely change the bit from different thread without worrying about corrupting nearby bits (and means threads changing other bit won't corrupt us). [1] Captured on a machine running a downstream 6.6 kernel [2] https://cs.android.com/android/platform/superproject/main/+/main:system/core/libmodprobe/libmodprobe.cpp?q=LoadModulesParallel Cc: stable@vger.kernel.org Fixes: 2023c610dc54 ("Driver core: add new device to bus's list before probing") Reviewed-by: Alan Stern Reviewed-by: Rafael J. Wysocki (Intel) Reviewed-by: Danilo Krummrich Acked-by: Greg Kroah-Hartman Acked-by: Marek Szyprowski Signed-off-by: Douglas Anderson Link: https://patch.msgid.link/20260406162231.v5.1.Id750b0fbcc94f23ed04b7aecabcead688d0d8c17@changeid Signed-off-by: Danilo Krummrich (cherry picked from commit a2225b6e834a838ae3c93709760edc0a169eb2f2) Signed-off-by: Douglas Anderson --- drivers/base/core.c | 15 ++++++++++++++ drivers/base/dd.c | 20 +++++++++++++++++++ include/linux/device.h | 44 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 79 insertions(+) diff --git a/drivers/base/core.c b/drivers/base/core.c index d985c4b87de5..112bca602253 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -3694,6 +3694,21 @@ int device_add(struct device *dev) fw_devlink_link_device(dev); } + /* + * The moment the device was linked into the bus's "klist_devices" in + * bus_add_device() then it's possible that probe could have been + * attempted in a different thread via userspace loading a driver + * matching the device. "ready_to_probe" being unset would have + * blocked those attempts. Now that all of the above initialization has + * happened, unblock probe. If probe happens through another thread + * after this point but before bus_probe_device() runs then it's fine. + * bus_probe_device() -> device_initial_probe() -> __device_attach() + * will notice (under device_lock) that the device is already bound. + */ + device_lock(dev); + dev_set_ready_to_probe(dev); + device_unlock(dev); + bus_probe_device(dev); /* diff --git a/drivers/base/dd.c b/drivers/base/dd.c index dbbe2cebb891..1c6f266f9367 100644 --- a/drivers/base/dd.c +++ b/drivers/base/dd.c @@ -770,6 +770,26 @@ static int __driver_probe_device(struct device_driver *drv, struct device *dev) if (dev->driver) return -EBUSY; + /* + * In device_add(), the "struct device" gets linked into the subsystem's + * list of devices and broadcast to userspace (via uevent) before we're + * quite ready to probe. Those open pathways to driver probe before + * we've finished enough of device_add() to reliably support probe. + * Detect this and tell other pathways to try again later. device_add() + * itself will also try to probe immediately after setting + * "ready_to_probe". + */ + if (!dev_ready_to_probe(dev)) + return dev_err_probe(dev, -EPROBE_DEFER, "Device not ready to probe\n"); + + /* + * Set can_match = true after calling dev_ready_to_probe(), so + * driver_deferred_probe_add() won't actually add the device to the + * deferred probe list when dev_ready_to_probe() returns false. + * + * When dev_ready_to_probe() returns false, it means that device_add() + * will do another probe() attempt for us. + */ dev->can_match = true; pr_debug("bus: '%s': %s: matched device %s with driver %s\n", drv->bus->name, __func__, dev_name(dev), drv->name); diff --git a/include/linux/device.h b/include/linux/device.h index cc84521795b1..528e0dad742e 100644 --- a/include/linux/device.h +++ b/include/linux/device.h @@ -457,6 +457,21 @@ struct device_physical_location { bool lid; }; +/** + * enum struct_device_flags - Flags in struct device + * + * Each flag should have a set of accessor functions created via + * __create_dev_flag_accessors() for each access. + * + * @DEV_FLAG_READY_TO_PROBE: If set then device_add() has finished enough + * initialization that probe could be called. + */ +enum struct_device_flags { + DEV_FLAG_READY_TO_PROBE = 0, + + DEV_FLAG_COUNT +}; + /** * struct device - The basic device structure * @parent: The device's "parent" device, the device to which it is attached. @@ -545,6 +560,7 @@ struct device_physical_location { * and optionall (if the coherent mask is large enough) also * for dma allocations. This flag is managed by the dma ops * instance from ->dma_supported. + * @flags: DEV_FLAG_XXX flags. Use atomic bitfield operations to modify. * * At the lowest level, every device in a Linux system is represented by an * instance of struct device. The device structure contains the information @@ -652,8 +668,36 @@ struct device { #ifdef CONFIG_DMA_OPS_BYPASS bool dma_ops_bypass : 1; #endif + + DECLARE_BITMAP(flags, DEV_FLAG_COUNT); }; +#define __create_dev_flag_accessors(accessor_name, flag_name) \ +static inline bool dev_##accessor_name(const struct device *dev) \ +{ \ + return test_bit(flag_name, dev->flags); \ +} \ +static inline void dev_set_##accessor_name(struct device *dev) \ +{ \ + set_bit(flag_name, dev->flags); \ +} \ +static inline void dev_clear_##accessor_name(struct device *dev) \ +{ \ + clear_bit(flag_name, dev->flags); \ +} \ +static inline void dev_assign_##accessor_name(struct device *dev, bool value) \ +{ \ + assign_bit(flag_name, dev->flags, value); \ +} \ +static inline bool dev_test_and_set_##accessor_name(struct device *dev) \ +{ \ + return test_and_set_bit(flag_name, dev->flags); \ +} + +__create_dev_flag_accessors(ready_to_probe, DEV_FLAG_READY_TO_PROBE); + +#undef __create_dev_flag_accessors + /** * struct device_link - Device link representation. * @supplier: The device on the supplier end of the link. -- 2.54.0.545.g6539524ca2-goog