From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Selvarasu Ganesan <selvarasu.g@samsung.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jh0801.jung@samsung.com" <jh0801.jung@samsung.com>,
"dh10.jung@samsung.com" <dh10.jung@samsung.com>,
"naushad@samsung.com" <naushad@samsung.com>,
"akash.m5@samsung.com" <akash.m5@samsung.com>,
"rc93.raju@samsung.com" <rc93.raju@samsung.com>,
"taehyun.cho@samsung.com" <taehyun.cho@samsung.com>,
"hongpooh.kim@samsung.com" <hongpooh.kim@samsung.com>,
"eomji.oh@samsung.com" <eomji.oh@samsung.com>,
"shijie.cai@samsung.com" <shijie.cai@samsung.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] usb: dwc3: core: Prevent USB core invalid event buffer address access
Date: Fri, 9 Aug 2024 23:28:12 +0000 [thread overview]
Message-ID: <20240809232804.or5kccyf7yebbqm6@synopsys.com> (raw)
In-Reply-To: <20240808120507.1464-1-selvarasu.g@samsung.com>
On Thu, Aug 08, 2024, Selvarasu Ganesan wrote:
> This commit addresses an issue where the USB core could access an
> invalid event buffer address during runtime suspend, potentially causing
> SMMU faults and other memory issues. The problem arises from the
> following sequence.
> 1. In dwc3_gadget_suspend, there is a chance of a timeout when
> moving the USB core to the halt state after clearing the
> run/stop bit by software.
> 2. In dwc3_core_exit, the event buffer is cleared regardless of
> the USB core's status, which may lead to an SMMU faults and
This is a workaround to your specific setup behavior. Please document in
the commit message which platforms are impacted.
> other memory issues. if the USB core tries to access the event
> buffer address.
>
> To prevent this issue, this commit ensures that the event buffer address
> is not cleared by software when the USB core is active during runtime
> suspend by checking its status before clearing the buffer address.
>
> Cc: stable@vger.kernel.org
We can keep the stable tag, but there's no issue with the commit below.
> Fixes: 89d7f9629946 ("usb: dwc3: core: Skip setting event buffers for host only controllers")
> Signed-off-by: Selvarasu Ganesan <selvarasu.g@samsung.com>
> ---
>
> Changes in v2:
> - Added separate check for USB controller status before cleaning the
> event buffer.
> - Link to v1: https://urldefense.com/v3/__https://lore.kernel.org/lkml/20240722145617.537-1-selvarasu.g@samsung.com/__;!!A4F2R9G_pg!cvZmnaxTWtJKR4ZDRZDa-8mvxpvkf5KPx57IwSXTSEtEFIVkPullR7sTYP0AM9de0xFbHLKdM_5jzBUiBL3f9SuioYE$
> ---
> drivers/usb/dwc3/core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 734de2a8bd21..5b67d9bca71b 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -564,10 +564,15 @@ int dwc3_event_buffers_setup(struct dwc3 *dwc)
> void dwc3_event_buffers_cleanup(struct dwc3 *dwc)
> {
> struct dwc3_event_buffer *evt;
> + u32 reg;
>
> if (!dwc->ev_buf)
> return;
>
Please add comment here why we need this and which platform is impacted
should we need to go back and test.
> + reg = dwc3_readl(dwc->regs, DWC3_DSTS);
> + if (!(reg & DWC3_DSTS_DEVCTRLHLT))
> + return;
> +
> evt = dwc->ev_buf;
>
> evt->lpos = 0;
> --
> 2.17.1
>
Thanks,
Thinh
next prev parent reply other threads:[~2024-08-09 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240808120605epcas5p2c9164533413706da5f7fa2ed624318cd@epcas5p2.samsung.com>
2024-08-08 12:05 ` [PATCH v2] usb: dwc3: core: Prevent USB core invalid event buffer address access Selvarasu Ganesan
2024-08-09 23:28 ` Thinh Nguyen [this message]
2024-08-10 15:09 ` Selvarasu Ganesan
2024-08-13 23:17 ` Thinh Nguyen
2024-08-14 4:59 ` Selvarasu Ganesan
2024-08-15 0:04 ` Thinh Nguyen
2024-08-15 4:49 ` Selvarasu Ganesan
2024-08-19 9:28 ` Krishna Kurapati
2024-08-20 23:03 ` Thinh Nguyen
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=20240809232804.or5kccyf7yebbqm6@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=akash.m5@samsung.com \
--cc=dh10.jung@samsung.com \
--cc=eomji.oh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=hongpooh.kim@samsung.com \
--cc=jh0801.jung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=naushad@samsung.com \
--cc=rc93.raju@samsung.com \
--cc=selvarasu.g@samsung.com \
--cc=shijie.cai@samsung.com \
--cc=stable@vger.kernel.org \
--cc=taehyun.cho@samsung.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