Re: [PATCH] usb: core: Emit KOBJ_CHANGE on unbound interface

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Tue, Oct 13, 2026 at 09:48:21AM -0700, Fabien Sanglard wrote:
> My original patch focuses on fixing the silent failure for usbfs
> drivers (like ADB). Since other drivers survive a reset without issues
> from a user space perspective, I wanted to avoid being disruptive to
> unaffected systems.
> 
> That said, unifying the behavior upon reset would be elegant. My main
> concern is whether some existing udev rules or netlink listeners in
> user space might break if we generalize this behavior and start
> emitting unexpected CHANGE events for interfaces that successfully
> rebound (which already emit UNBIND -> BIND).
> 
> But it might be worth "trying". I am unsure what the kernel team
> philosophy is in this regard. If you all agree, we could trigger the
> KOBJ_CHANGE event unconditionally inside rebind_marked_interfaces()
> instead of conditionally inside usb_rebind_intf().

Please try and test to verify.

thanks,

greg k-h