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>,
"Johan Hovold" <johan@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<driver-core@lists.linux.dev>, <linux-usb@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 7.4-rc1
Date: Sun, 25 Oct 2026 21:16:37 +0100 [thread overview]
Message-ID: <DME7288WXCGZ.1XSS13X4IVJ5W@kernel.org> (raw)
Hi Linus,
Please pull these driver-core fixes.
These fixes arrived late in the cycle and missed the main driver-core pull
request for 7.4-rc1.
Thanks,
Danilo
The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:
Linux 7.3-rc5 (2026-09-27 13:55:01 -0700)
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.4-rc1-2
for you to fetch changes up to 187a62f99da29b1a55602b0d401a783d8dc86161:
driver core: take parent lock in async device attach (2026-10-16 22:36:09 +0200)
----------------------------------------------------------------
Driver core fixes for 7.4-rc1
- Make parent-lock requirements per device type instead of per bus,
fixing a use-after-free on USB disconnect by limiting the requirement
to USB interfaces, which retain a reference to their parent
- Honor parent-lock requirements during deferred and asynchronous
probing, fixing USB interface probe races, including duplicate
endpoint creation attempts in sysfs
----------------------------------------------------------------
Johan Hovold (2):
driver core: fix parent lock use-after-free on USB disconnect
driver core: take parent lock on deferred probe
Mario Peter (1):
driver core: take parent lock in async device attach
drivers/base/base.h | 1 +
drivers/base/bus.c | 32 +++++++++++++++++++++++---------
drivers/base/dd.c | 90 +++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------
drivers/usb/core/driver.c | 1 -
drivers/usb/core/message.c | 1 +
include/linux/device.h | 5 +++++
include/linux/device/bus.h | 3 ---
7 files changed, 79 insertions(+), 54 deletions(-)
next reply other threads:[~2026-10-25 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 20:16 Danilo Krummrich [this message]
2026-10-26 17:25 ` 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=DME7288WXCGZ.1XSS13X4IVJ5W@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®