From: sashiko-bot@kernel.org
To: "Joe Finzel" <joe@sudmix.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: core: sysfs: show product, manufacturer and serial without the device lock
Date: Wed, 14 Oct 2026 21:09:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-171920@kernel.org> (raw)
In-Reply-To: <20261014-usb-string-attrs-v2-1-c5cacdad7094@sudmix.de>
> From: Joe Finzel <joe@sudmix.de>
>
> Reading the product, manufacturer or serial attribute of a USB device
> takes the device lock. A hub holds its lock in hub_event() while it
> enumerates all of its ports, including the debounce and reset delays of
> every child, so a reader of the hub's strings waits until the last port
> is done -- seconds on a hub with several devices.
>
> udev reads these strings for every USB device (the usb_id builtin, run
> from 50-udev-default.rules). Its worker blocks SIGTERM, so when systemd
> stops udevd in the initrd before switching root, it waits for that
> worker. On a desktop with a few hubs this delays every boot:
>
> i7-13700K, ASUS ROG STRIX Z790-F, four hubs with HID devices behind
> them: udevd took 1.7 s to stop, while the hubs were still enumerating.
> [ ... ]
> USB product/manufacturer/serial handling to RCU"); back then the strings
> could still change under Wireless USB.
>
> Reviewed-by: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: Joe Finzel <joe@sudmix.de>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014-usb-string-attrs-v2-1-c5cacdad7094@sudmix.de?part=1
prev parent reply other threads:[~2026-10-14 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:01 [PATCH v2] usb: core: sysfs: show product, manufacturer and serial without the device lock Joe Finzel via B4 Relay
2026-10-14 21:09 ` sashiko-bot [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=sashiko-outbox-171920@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=joe@sudmix.de \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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