All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Mario Peter" <mario.peter@leica-geosystems.com>,
	<driver-core@lists.linux.dev>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] driver core: parent lock fixes
Date: Thu, 15 Oct 2026 01:11:47 +0200	[thread overview]
Message-ID: <DM4XWCTH7UBK.3HO753UD4MCRY@kernel.org> (raw)
In-Reply-To: <20261014133109.1392265-1-johan@kernel.org>

On Wed Oct 14, 2026 at 3:31 PM CEST, Johan Hovold wrote:
> Mario Peter reported that USB interfaces may be probed without holding
> the parent USB device lock during asynchronous and deferred probe.
>
> This series addresses both cases, while fixing a long-standing
> use-after-free issue with the parent lock implementation stemming from
> the fact that the driver core does not necessarily hold a reference to
> the parent device when taking its lock.

I've picked those fixes up, as I think it would be good to still land them for
v7.4-rc1. (I might send them as a second PR in the middle of the merge window
though.)

Please let me know in case you have any concerns.

Thanks,
Danilo

  parent reply	other threads:[~2026-10-14 23:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 13:31 [PATCH v2 0/3] driver core: parent lock fixes Johan Hovold
2026-10-14 13:31 ` [PATCH v2 1/3] driver core: fix parent lock use-after-free on USB disconnect Johan Hovold
2026-10-14 13:43   ` sashiko-bot
2026-10-14 14:49   ` Danilo Krummrich
2026-10-14 14:58     ` Alan Stern
2026-10-14 13:31 ` [PATCH v2 2/3] driver core: take parent lock on deferred probe Johan Hovold
2026-10-14 13:48   ` sashiko-bot
2026-10-14 13:31 ` [PATCH v2 3/3] driver core: take parent lock in async device attach Johan Hovold
2026-10-14 13:40   ` sashiko-bot
2026-10-14 14:52   ` Alan Stern
2026-10-14 14:58     ` Johan Hovold
2026-10-14 23:11 ` Danilo Krummrich [this message]
2026-10-14 23:12 ` [PATCH v2 0/3] driver core: parent lock fixes Danilo Krummrich

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=DM4XWCTH7UBK.3HO753UD4MCRY@kernel.org \
    --to=dakr@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --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=mario.peter@leica-geosystems.com \
    --cc=rafael@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.