public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Rechberger <linuxusb.ml@sundtek.de>
To: Mathias Nyman <mathias.nyman@linux.intel.com>,
	 linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] XHCI NULL Pointer check in xhci_check_bw_table
Date: Mon, 18 Nov 2024 17:51:08 +0800	[thread overview]
Message-ID: <4ce9b10dff6eecf78cee53b6f34d4e6f8df37b59.camel@sundtek.de> (raw)
In-Reply-To: <a02cfe06-b227-431f-baa1-a504857a8dea@linux.intel.com>

On Mon, 2024-11-18 at 11:36 +0200, Mathias Nyman wrote:
> Hi
> 
> On 17.11.2024 17.32, Sundtek wrote:
> > This patch fixes a NULL Pointer exception when a device using the
> > XHCI
> > controller driver is not properly initialized. It's relatively easy
> > to
> > reproduce with a faulty connection to a USB Harddisk / USB Ethernet
> > adapter.
> > The way I used for testing this patch was to short USB D+/D- and
> > pull
> > them to ground.
> > 
> > We manufacture our own USB devices and use Linux for testing,
> > lately we
> > upgraded the system to Ubuntu noble with Kernel 6.8.0 and our
> > system
> > also crashed multiple times just when plugging in some devices (no
> > commands need to be executed).
> > We connect/disconnect devices > 100 times (eg uploading firmware,
> > do
> > electrical tests etc).
> > 
> > I would rate this issue as highly critical.
> > The problem is triggered via some fallback code in hub.c, a second
> > patch will follow which
> > removes the endpoint reset in the particular fallback.
> > 
> 
> 
> > 2024-11-16T22:14:12.122224+08:00 sundtek-UX32VD kernel: RIP:
> > 0010:xhci_check_bw_table+0x100/0x4d0
> 
> This looks very similar to a null pointer issue I fixed recently.
> Patch should be in 6.11 and recent stable releases:
> 
> af8e119f52e9 xhci: Fix Panther point NULL pointer deref at full-speed
> re-enumeration
> 
> What kernel are you running?


thanks for pointing out to that, I was testing this on Linux 6.8.12.
I will recompile the latest kernel and double check.

your one:
[46711.125623] Workqueue: usb_hub_wq hub_event [usbcore]
[46711.125668] RIP: 0010:xhci_reserve_bandwidth
(drivers/usb/host/xhci.c

vs my one:
kernel: Workqueue: usb_hub_wq hub_event
kernel: RIP: 0010:xhci_check_bw_table+0x100/0x4d0

https://sundtek.de/support/uxvd32.txt

Best Regards,
Markus

> 
> Thanks
> Mathias


  reply	other threads:[~2024-11-18  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 15:32 [PATCH] XHCI NULL Pointer check in xhci_check_bw_table Sundtek
2024-11-17 19:21 ` Greg KH
2024-11-17 23:27 ` Markus Rechberger
2024-11-18  6:30   ` Greg KH
2024-11-18  6:48     ` Markus Rechberger
2024-11-18  6:55       ` Greg KH
2024-11-18  8:03         ` Markus Rechberger
2024-11-18  9:36 ` Mathias Nyman
2024-11-18  9:51   ` Markus Rechberger [this message]
2024-11-18 10:23     ` Markus Rechberger

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=4ce9b10dff6eecf78cee53b6f34d4e6f8df37b59.camel@sundtek.de \
    --to=linuxusb.ml@sundtek.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.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