Files
linux-stable-mirror/include/linux
Danilo Krummrich 78aba57ca3 driver core: generalize driver_override in struct device
[ Upstream commit cb3d1049f4 ]

Currently, there are 12 busses (including platform and PCI) that
duplicate the driver_override logic for their individual devices.

All of them seem to be prone to the bug described in [1].

While this could be solved for every bus individually using a separate
lock, solving this in the driver-core generically results in less (and
cleaner) changes overall.

Thus, move driver_override to struct device, provide corresponding
accessors for busses and handle locking with a separate lock internally.

In particular, add device_set_driver_override(),
device_has_driver_override(), device_match_driver_override() and
generalize the sysfs store() and show() callbacks via a driver_override
feature flag in struct bus_type.

Until all busses have migrated, keep driver_set_override() in place.

Note that we can't use the device lock for the reasons described in [2].

Link: https://bugzilla.kernel.org/show_bug.cgi?id=220789 [1]
Link: https://lore.kernel.org/driver-core/DGRGTIRHA62X.3RY09D9SOK77P@kernel.org/ [2]
Tested-by: Gui-Dong Han <hanguidong02@gmail.com>
Co-developed-by: Gui-Dong Han <hanguidong02@gmail.com>
Signed-off-by: Gui-Dong Han <hanguidong02@gmail.com>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://patch.msgid.link/20260303115720.48783-2-dakr@kernel.org
[ Use dev->bus instead of sp->bus for consistency; fix commit message to
  refer to the struct bus_type's driver_override feature flag. - Danilo ]
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Stable-dep-of: 2b38efc05b ("driver core: platform: use generic driver_override infrastructure")
Signed-off-by: Sasha Levin <sashal@kernel.org>
2026-04-02 13:09:25 +02:00
..
2026-03-04 07:19:39 -05:00
2026-03-04 07:20:22 -05:00
2026-03-04 07:19:26 -05:00
2025-11-02 22:15:22 +09:00
2025-10-15 12:00:03 +02:00
2025-03-07 18:25:35 +01:00
2025-09-11 17:21:46 +02:00
2025-12-18 13:55:17 +01:00
2025-05-29 11:03:25 +02:00
2026-01-08 10:13:54 +01:00
2026-01-08 10:14:34 +01:00
2025-09-09 18:58:04 +02:00
2025-05-29 11:03:25 +02:00
2025-05-29 11:02:23 +02:00
2025-03-28 22:03:30 +01:00
2025-12-18 13:55:18 +01:00
2025-06-19 15:32:18 +02:00
2026-02-11 13:40:25 +01:00
2025-05-29 11:02:20 +02:00
2025-08-15 12:13:35 +02:00
2026-01-08 10:14:11 +01:00
2026-02-11 13:40:25 +01:00
2026-03-04 07:19:35 -05:00
2025-08-01 09:48:43 +01:00