From: sashiko-bot@kernel.org
To: "Fabien Sanglard" <sanglardf@google.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: core: Emit KOBJ_CHANGE on unbound interface
Date: Mon, 12 Oct 2026 17:28:10 +0000 [thread overview]
Message-ID: <sashiko-outbox-168454@kernel.org> (raw)
In-Reply-To: <20261012171609.88273-1-sanglardf@google.com>
> When an interface driver is forcibly unbound before a device reset,
> usb_rebind_intf() attempts to re-attach a driver once the reset
> completes in-place. Normal kernel drivers rebind and emit UNBIND
> followed by BIND. However, usbfs only binds on explicit userspace
> requests (e.g., USBDEVFS_CLAIMINTERFACE), so device_attach() returns 0
> and no uevent is emitted.
>
> As a result, userspace clients like adb only see UNBIND and must poll
> /dev/bus/usb to detect when the interface is ready again. Emit a
> KOBJ_CHANGE uevent when device_attach() finds no matching driver so
> userspace is notified that the interface can be reclaimed.
>
> Link: https://lore.kernel.org/linux-usb/CAA92w6k-LA4tVXyX1mFNOR3e+_mC43F_BXqhXeWqQyFx2D4_Mg@mail.gmail.com/
> Signed-off-by: Fabien Sanglard <sanglardf@google.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261012171609.88273-1-sanglardf@google.com?part=1
next prev parent reply other threads:[~2026-10-12 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 21:48 Missing uevents after successful USBDEVFS_RESET Fabien Sanglard
2026-09-16 2:37 ` Alan Stern
2026-09-20 6:00 ` Fabien Sanglard
2026-09-20 14:58 ` Alan Stern
2026-10-12 17:16 ` [PATCH] usb: core: Emit KOBJ_CHANGE on unbound interface Fabien Sanglard
2026-10-12 17:28 ` sashiko-bot [this message]
2026-10-13 9:34 ` Oliver Neukum
2026-10-13 16:48 ` Fabien Sanglard
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-168454@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sanglardf@google.com \
--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