From: Greg KH <gregkh@linuxfoundation.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: "Johannes Brüderl" <johannes.bruederl@gmail.com>,
"Michal Pecio" <michal.pecio@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor
Date: Tue, 9 Dec 2025 05:46:56 +0900 [thread overview]
Message-ID: <2025120941-unhappily-smilingly-59e9@gregkh> (raw)
In-Reply-To: <dacafa36-10dc-4f2a-95fd-10ff785e4670@suse.com>
On Mon, Dec 08, 2025 at 09:58:55AM +0100, Oliver Neukum wrote:
> On 07.12.25 22:12, Greg KH wrote:
> > Ok, I can duplicate this here. Maybe we just don't ask for the BOS
> > descriptor if no one needs/asks for it. I can play with that later and
> > see if that helps as I'm sure this isn't going to be the only device
> > that can't handle the BOS descriptor if Windows isn't querying for it,
> > so we don't want to make a huge quirk table if we don't have to.
>
> 1. That means we'd let lsusb crash devices. Not a good idea.
I don't think that it will crash. hopefully not, as just reading a
descriptor after enumerated shouldn't cause that. I'll test it out...
> 2. It is, unfortunately, possible that firmware authors simply
> script a detection sequence. That means devices would crash
> if you request a descriptor at a time when Windows would not
> request it, not just in general.
> I am afraid I need to point you at the horrible example
> of HID_ALWAYS_POLL
That is horrible, hopefully we don't have to do that here :(
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-08 20:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 0:00 [PATCH] usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor Johannes Brüderl
2025-12-07 0:15 ` Greg KH
2025-12-07 1:20 ` [PATCH v2] " Johannes Brüderl
2025-12-07 6:19 ` Lars Melin
2025-12-07 9:02 ` [PATCH v3 1/1] " Johannes Brüderl
2026-01-07 16:06 ` Greg KH
2025-12-07 7:40 ` [PATCH v2] " Michal Pecio
2025-12-07 9:22 ` Johannes Brüderl
2025-12-07 9:45 ` Michal Pecio
2025-12-07 10:47 ` Johannes Brüderl
2025-12-07 11:00 ` Greg KH
2025-12-07 21:12 ` Greg KH
2025-12-07 22:06 ` Michal Pecio
2025-12-08 8:58 ` Oliver Neukum
2025-12-08 20:46 ` Greg KH [this message]
2025-12-28 12:54 ` Johannes Brüderl
2025-12-28 13:18 ` Greg KH
2025-12-07 0:37 ` [PATCH] " Michal Pecio
2025-12-07 0:59 ` Greg KH
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=2025120941-unhappily-smilingly-59e9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes.bruederl@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=oneukum@suse.com \
/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