From: Daniel Golle <daniel@makrotopia.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Hans de Goede <hansg@kernel.org>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 0/4] device_schedule_reprobe(): core helper and conversions
Date: Tue, 10 Nov 2026 10:21:35 +0000 [thread overview]
Message-ID: <avLv6TwefQu-GPWp@makrotopia.org> (raw)
In-Reply-To: <cover.1792203271.git.daniel@makrotopia.org>
Hi Greg,
On Sat, Oct 17, 2026 at 09:55:17AM +0100, Daniel Golle wrote:
> iwlwifi and hci_h5 re-probe their own device from a work item in module
> text ending in module_put(THIS_MODULE), which a concurrent rmmod can
> race, and nothing ties the re-probe to the binding that asked for it.
> btintel_pcie re-probes synchronously from its own reset work. This
> series adds device_schedule_reprobe() to the driver core and converts
> all three.
>
> Tested on an Intel AX101 with patches 1 to 3, PROVE_LOCKING and
> DEBUG_OBJECTS_WORK: a re-probe, and an unbind, rmmod, PCI removal,
> suspend and reboot with one pending. The unbind and the removals
> cancelled it, and it ran after resume. The stock iwlwifi code undid
> the unbind, and rmmod with its work held just past module_put() oopsed
> in lockdep. Patches 3 and 4 are untested for lack of hardware.
Now that the most hardcore merge-window ever is over and v7.4-rc1 is
out, can you take a look at this?
The series has received positive feedback and was tested by some more
of the bluetooth folks by now, and is immediately useful to address
currently buggy behavior of existing popular driver, and prevent the
same wrong pattern from being duplicated into new drivers.
Cheers
Daniel
prev parent reply other threads:[~2026-11-10 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 8:55 Daniel Golle
2026-10-17 8:56 ` [PATCH v4 1/4] driver core: add device_schedule_reprobe() Daniel Golle
2026-10-25 21:29 ` Nikolay Bryskin
2026-10-17 8:56 ` [PATCH v4 2/4] wifi: iwlwifi: use device_schedule_reprobe() Daniel Golle
2026-10-17 8:56 ` [PATCH v4 3/4] Bluetooth: hci_h5: " Daniel Golle
2026-10-17 8:57 ` [PATCH v4 4/4] Bluetooth: btintel_pcie: use device_schedule_reprobe() after reset Daniel Golle
2026-11-10 10:21 ` Daniel Golle [this message]
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=avLv6TwefQu-GPWp@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=rafael@kernel.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®