public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Bence Csókás" <bence98@sch.bme.hu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: core: Use `krealloc()` in `usb_cache_string()`
Date: Sun, 15 Mar 2026 11:47:36 +0100	[thread overview]
Message-ID: <2026031547-carve-resale-68dc@gregkh> (raw)
In-Reply-To: <45afec49-3fe7-43c7-b92b-e6c3e4aca3d3@sch.bme.hu>

On Sun, Mar 15, 2026 at 11:34:52AM +0100, Bence Csókás wrote:
> 
> 
> On 3/15/26 10:59, Bence Csókás wrote:
> > Hi,
> > 
> > On 3/15/26 10:47, Greg Kroah-Hartman wrote:
> > > On Sun, Mar 15, 2026 at 10:40:48AM +0100, Bence Csókás wrote:
> > > > > Also, how was this tested?
> > > > 
> > > > I just compiled and booted it on my Arch box (with the original vendor
> > > > config), an AthlonII X2 PC. I'm now typing this mail on a USB
> > > > keyboard and
> > > > mouse under Plasma, running this kernel :) I also plugged in a pendrive,
> > > > mounted it, `ls`'d the mount, unmounted, unplugged, and did this 2 more
> > > > times.
> > > > 
> > > > I realize I should probably put this info under the dashes. I'll
> > > > prepare a
> > > > v2.
> > > 
> > > Try looking at the USB strings in the device, as that's the path here
> > > that is exercised.  Just using the device doesn't actually grab them
> > > from the descriptor table.
> > 
> > Sure.
> > 
> >    $ sudo lsusb -vvv | grep iProduct
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 OHCI PCI host controller
> >      iProduct                2 HP USB Smart Card Keyboard
> >    can't get device qualifier: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 USB OPTICAL MOUSE
> >    can't get debug descriptor: Resource temporarily unavailable
> >    can't get device qualifier: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 EHCI Host Controller
> >      iProduct                2 EHCI Host Controller
> >    can't get device qualifier: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 Disk 2.0
> >      iProduct                2 EHCI Host Controller
> >    can't get device qualifier: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 OHCI PCI host controller
> >      iProduct                2 OHCI PCI host controller
> >    can't get debug descriptor: Resource temporarily unavailable
> >    can't get debug descriptor: Resource temporarily unavailable
> >      iProduct                2 OHCI PCI host controller
> > 
> > Are these -EAGAINs cause for concern?
> 
> It happens with the vendor kernel (6.19.8-arch1-1) too, so it's probably
> just some weirdness in my HW...

You can't get the debug descriptor when a driver is bound to the device.
Also look at the iManufacturer string, that should be coming from the
device (except for the root hub, that descriptor comes from the kernel.)

thanks,

greg k-h

      reply	other threads:[~2026-03-15 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 23:06 [PATCH] USB: core: Use `krealloc()` in `usb_cache_string()` Bence Csókás via B4 Relay
2026-03-12  5:02 ` Greg Kroah-Hartman
2026-03-15  9:40   ` Bence Csókás
2026-03-15  9:47     ` Greg Kroah-Hartman
2026-03-15  9:59       ` Bence Csókás
2026-03-15 10:34         ` Bence Csókás
2026-03-15 10:47           ` Greg Kroah-Hartman [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=2026031547-carve-resale-68dc@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bence98@sch.bme.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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