From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Meng Li <Meng.Li@windriver.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"quic_uaggarwa@quicinc.com" <quic_uaggarwa@quicinc.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xu.yang_2@nxp.com" <xu.yang_2@nxp.com>
Subject: Re: [v2 PATCH] usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock
Date: Tue, 18 Jun 2024 21:54:03 +0000 [thread overview]
Message-ID: <20240618215356.hw6ar6guxbhlf5y7@synopsys.com> (raw)
In-Reply-To: <20240618031918.2585799-1-Meng.Li@windriver.com>
On Tue, Jun 18, 2024, Meng Li wrote:
> When config CONFIG_USB_DWC3_DUAL_ROLE is selected, and trigger system
> to enter suspend status with below command:
> echo mem > /sys/power/state
> There will be a deadlock issue occurring. Detailed invoking path as
> below:
> dwc3_suspend_common()
> spin_lock_irqsave(&dwc->lock, flags); <-- 1st
> dwc3_gadget_suspend(dwc);
> dwc3_gadget_soft_disconnect(dwc);
> spin_lock_irqsave(&dwc->lock, flags); <-- 2nd
> This issue is exposed by commit c7ebd8149ee5 ("usb: dwc3: gadget: Fix
> NULL pointer dereference in dwc3_gadget_suspend") that removes the code
> of checking whether dwc->gadget_driver is NULL or not. It causes the
> following code is executed and deadlock occurs when trying to get the
> spinlock. In fact, the root cause is the commit 5265397f9442("usb: dwc3:
> Remove DWC3 locking during gadget suspend/resume") that forgot to remove
> the lock of otg mode. So, remove the redundant lock of otg mode during
> gadget suspend/resume.
>
> Fixes: 5265397f9442 ("usb: dwc3: Remove DWC3 locking during gadget suspend/resume")
> Cc: Xu Yang <xu.yang_2@nxp.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Meng Li <Meng.Li@windriver.com>
>
> ---
> v1->v2:
> - improve commit log, correct the Fixes commit id.
>
> ---
> drivers/usb/dwc3/core.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 7ee61a89520b..9d47c3aa5777 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -2250,7 +2250,6 @@ static int dwc3_core_init_for_resume(struct dwc3 *dwc)
>
> static int dwc3_suspend_common(struct dwc3 *dwc, pm_message_t msg)
> {
> - unsigned long flags;
> u32 reg;
> int i;
>
> @@ -2293,9 +2292,7 @@ static int dwc3_suspend_common(struct dwc3 *dwc, pm_message_t msg)
> break;
>
> if (dwc->current_otg_role == DWC3_OTG_ROLE_DEVICE) {
> - spin_lock_irqsave(&dwc->lock, flags);
> dwc3_gadget_suspend(dwc);
> - spin_unlock_irqrestore(&dwc->lock, flags);
> synchronize_irq(dwc->irq_gadget);
> }
>
> @@ -2312,7 +2309,6 @@ static int dwc3_suspend_common(struct dwc3 *dwc, pm_message_t msg)
>
> static int dwc3_resume_common(struct dwc3 *dwc, pm_message_t msg)
> {
> - unsigned long flags;
> int ret;
> u32 reg;
> int i;
> @@ -2366,9 +2362,7 @@ static int dwc3_resume_common(struct dwc3 *dwc, pm_message_t msg)
> if (dwc->current_otg_role == DWC3_OTG_ROLE_HOST) {
> dwc3_otg_host_init(dwc);
> } else if (dwc->current_otg_role == DWC3_OTG_ROLE_DEVICE) {
> - spin_lock_irqsave(&dwc->lock, flags);
> dwc3_gadget_resume(dwc);
> - spin_unlock_irqrestore(&dwc->lock, flags);
> }
>
> break;
> --
> 2.34.1
>
Did you use "git format-patch -v"? The $subject version prefix order is
different. In any case,
Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Thanks,
Thinh
next prev parent reply other threads:[~2024-06-18 21:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 3:19 [v2 PATCH] usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock Meng Li
2024-06-18 21:54 ` Thinh Nguyen [this message]
2024-06-18 22:19 ` Michael Nazzareno Trimarchi
2024-06-18 22:42 ` Thinh Nguyen
2024-06-18 22:55 ` Michael Nazzareno Trimarchi
2024-06-18 23:05 ` Thinh Nguyen
2024-06-19 1:48 ` Li, Meng
2024-06-19 2:02 ` Li, Meng
2024-06-21 23:14 ` Thinh Nguyen
2024-06-22 4:14 ` Li, Meng
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=20240618215356.hw6ar6guxbhlf5y7@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=Meng.Li@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_uaggarwa@quicinc.com \
--cc=xu.yang_2@nxp.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