From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: list_del corruption (NULL pointer dereference) on xhci-pci unbind
Date: Fri, 14 Oct 2022 22:29:36 +0200 [thread overview]
Message-ID: <Y0nGsKipsnl3gtrp@mail-itl> (raw)
In-Reply-To: <7eaf9861-5571-584f-b124-fa7076920090@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On Fri, Oct 14, 2022 at 07:02:13PM +0300, Mathias Nyman wrote:
> This whole software bandwidth issue should only be visible in Intel
> Panther Point PCH xHC (Ivy bridge)
It is indeed Ivy Bridge platform.
> Endpoints should be deleted from bw_table list, and xhci_virt_devices
> should be freed already before xhci_mem_cleanup() is called if all goes well.
>
> Normally endpoints are deleted from bw_table list during usb_disconnect()
>
> usb_disconnect()
> ...
> usb_hcd_alloc_bandwidth(dev, NULL, NULL, NULL);
> hcd->driver->drop_endpoint() // flags endpoint to be dropped
> hcd->driver->check_bandwidth()
> ->xhci_check_bandwidth()
> xhci_configure_endpoint()
> xhci_reserve_bandwidth() // only for Panther Point
> xhci_drop_ep_from_interval_table()
>
> But to avoid queuing new commands to a host in XHCI_STATE_DYING or
> XHCI_STATE_REMOVING state we return early, not calling xhci_reserve_bandwidth().
Indeed when I remove that early return in xhci_check_bandwidth(), the
crash is gone. What's the proper solution?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-14 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 0:31 list_del corruption (NULL pointer dereference) on xhci-pci unbind Marek Marczykowski-Górecki
2022-10-14 1:21 ` Marek Marczykowski-Górecki
2022-10-14 16:02 ` Mathias Nyman
2022-10-14 20:29 ` Marek Marczykowski-Górecki [this message]
2022-10-17 16:12 ` Mathias Nyman
2022-10-17 18:43 ` Marek Marczykowski-Górecki
2022-10-18 13:36 ` Mathias Nyman
2022-10-18 13:58 ` Marek Marczykowski-Górecki
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=Y0nGsKipsnl3gtrp@mail-itl \
--to=marmarek@invisiblethingslab.com \
--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