From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: henryl <henryl@nvidia.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-usb@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: tegra: fix checked USB2 port number
Date: Fri, 11 Oct 2024 10:03:32 +0200 [thread overview]
Message-ID: <2024101116-popper-grid-1e58@gregkh> (raw)
In-Reply-To: <20241011072240.42978-1-henryl@nvidia.com>
On Fri, Oct 11, 2024 at 03:22:40PM +0800, henryl wrote:
> From: Henry Lin <henryl@nvidia.com>
>
> USB2 root hub in VF may contain less port number than supported USB2
> phy number. Checking all USB2 phy number here would cause invalid
> memory access.
>
> [ 116.923438] Unable to handle kernel paging request at virtual address 006c622f7665642f
> ...
> [ 117.213640] Call trace:
> [ 117.216783] tegra_xusb_enter_elpg+0x23c/0x658
> [ 117.222021] tegra_xusb_runtime_suspend+0x40/0x68
> [ 117.227260] pm_generic_runtime_suspend+0x30/0x50
> [ 117.232847] __rpm_callback+0x84/0x3c0
> [ 117.237038] rpm_suspend+0x2dc/0x740
> [ 117.241229] pm_runtime_work+0xa0/0xb8
> [ 117.245769] process_scheduled_works+0x24c/0x478
> [ 117.251007] worker_thread+0x23c/0x328
> [ 117.255547] kthread+0x104/0x1b0
> [ 117.259389] ret_from_fork+0x10/0x20
> [ 117.263582] Code: 54000222 f9461ae8 f8747908 b4ffff48 (f9400100)
>
> Signed-off-by: Henry Lin <henryl@nvidia.com>
What commit id does this fix? Should it be backported?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-11 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 7:22 [PATCH] xhci: tegra: fix checked USB2 port number henryl
2024-10-11 8:03 ` Greg Kroah-Hartman [this message]
2024-10-11 8:32 ` Henry Lin
2024-10-11 8:44 ` Greg Kroah-Hartman
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=2024101116-popper-grid-1e58@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=henryl@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).