From: "Danilo Krummrich" <dakr@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<driver-core@lists.linux.dev>, <rust-for-linux@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 7.0-rc3
Date: Sat, 07 Mar 2026 12:39:17 +0100 [thread overview]
Message-ID: <DGWIRQLTVEK8.24EJBMC8LDQWJ@kernel.org> (raw)
Hi Linus,
Please pull the following revert; no other fixes included.
It has been in linux-next for a couple rounds; no conflicts expected.
Please expect a follow-up regarding the driver_override issue for likely
-rc4 or -rc5.
- Danilo
The following changes since commit 11439c4635edd669ae435eec308f4ab8a0804808:
Linux 7.0-rc2 (2026-03-01 15:39:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-7.0-rc3
for you to fetch changes up to 9de68394a61528d40f575c3e6719cc75c56f62c3:
Revert "driver core: enforce device_lock for driver_match_device()" (2026-03-03 13:12:42 +0100)
----------------------------------------------------------------
Driver core fixes for 7.0-rc3
- Revert "driver core: enforce device_lock for driver_match_device()":
When a device is already present in the system and a driver is
registered on the same bus, we iterate over all devices registered on
this bus to see if one of them matches. If we come across an already
bound one where the corresponding driver crashed while holding the
device lock (e.g. in probe()) we can't make any progress anymore.
Thus, revert and clarify that an implementer of struct bus_type must
not expect match() to be called with the device lock held.
----------------------------------------------------------------
Danilo Krummrich (1):
Revert "driver core: enforce device_lock for driver_match_device()"
drivers/base/base.h | 11 +----------
drivers/base/dd.c | 2 +-
include/linux/device/bus.h | 2 ++
3 files changed, 4 insertions(+), 11 deletions(-)
next reply other threads:[~2026-03-07 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 11:39 Danilo Krummrich [this message]
2026-03-07 20:00 ` [GIT PULL] Driver core fixes for 7.0-rc3 pr-tracker-bot
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=DGWIRQLTVEK8.24EJBMC8LDQWJ@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@kernel.org \
--cc=torvalds@linux-foundation.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