From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Prashanth K <prashanth.k@oss.qualcomm.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: host: Mark dwc->xhci as null if xhci probe fails
Date: Wed, 14 Oct 2026 13:17:22 +0200 [thread overview]
Message-ID: <2026101452-wow-scarecrow-c7d8@gregkh> (raw)
In-Reply-To: <20261014105711.1708244-1-prashanth.k@oss.qualcomm.com>
On Wed, Oct 14, 2026 at 04:27:11PM +0530, Prashanth K wrote:
> Currently dwc->xhci is not cleared when xhci_plat_probe fails,
> leading to null pointer dereference in dwc3_qcom_read_usb2_speed.
Why would that happen? What causes it and requires it?
> Mark the xhci pointer as NULL to prevent this.
>
> Signed-off-by: Prashanth K <prashanth.k@oss.qualcomm.com>
What commit id does this fix?
How was it tested?
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-14 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:57 [PATCH] usb: dwc3: host: Mark dwc->xhci as null if xhci probe fails Prashanth K
2026-10-14 11:07 ` sashiko-bot
2026-10-14 11:17 ` Greg Kroah-Hartman [this message]
2026-10-14 11:25 ` Prashanth K
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=2026101452-wow-scarecrow-c7d8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prashanth.k@oss.qualcomm.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