From: Danilo Krummrich <danilokrummrich@dk-develop.de>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org, balbi@kernel.org,
k.opasiak@samsung.com
Cc: Danilo Krummrich <danilokrummrich@dk-develop.de>
Subject: [PATCH] usb: gadget: udc: udc_stop before gadget unbind
Date: Mon, 14 Aug 2017 18:36:52 +0200 [thread overview]
Message-ID: <20170814163652.29108-1-danilokrummrich@dk-develop.de> (raw)
udc_stop needs to be called before gadget driver unbind. Otherwise it
might happen that udc drivers still call into the gadget driver (e.g.
to reset gadget after OTG event). If this happens it is likely to get
panics from gadget driver dereferencing NULL ptr, as gadget's drvdata
is set to NULL on unbind.
Signed-off-by: Danilo Krummrich <danilokrummrich@dk-develop.de>
---
Actually there could still be a race:
(CPU1 code taken from dwc3 drivers dwc3_disconnect_gadget() as exsample)
CPU0 CPU1
---- ----
usb_gadget_disconnect(udc->gadget);
udc->driver->disconnect(udc->gadget);
if (dwc->gadget_driver && dwc->gadget_driver->disconnect)
usb_gadget_udc_stop(udc);
udc->driver->unbind(udc->gadget);
dwc->gadget_driver->disconnect(&dwc->gadget);
UDC drivers typically set their gadget driver pointer to NULL in udc_stop
and check for it before calling into the gadget driver. To fix the issue
above every udc driver could apply a lock around this.
If you see the need for having this or another solutions I can provide
further patches. This patch could also just serve as a base for discussion
if someone knows a smarter solution.
I saw this problem causing a panic on hikey960 board and provided a quick
workaround for the same problem here:
https://android-review.googlesource.com/#/c/kernel/common/+/457476/
(panic log in the commit message of the linked patch)
---
drivers/usb/gadget/udc/core.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c
index efce68e9a8e0..8155468afc0d 100644
--- a/drivers/usb/gadget/udc/core.c
+++ b/drivers/usb/gadget/udc/core.c
@@ -1234,8 +1234,12 @@ static void usb_gadget_remove_driver(struct usb_udc *udc)
usb_gadget_disconnect(udc->gadget);
udc->driver->disconnect(udc->gadget);
- udc->driver->unbind(udc->gadget);
+ /* udc_stop needs to be called before gadget driver unbind to prevent
+ * udc driver calls into gadget driver after unbind which could cause
+ * a nullptr exception.
+ */
usb_gadget_udc_stop(udc);
+ udc->driver->unbind(udc->gadget);
udc->driver = NULL;
udc->dev.driver = NULL;
--
2.14.1
next reply other threads:[~2017-08-14 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 16:36 Danilo Krummrich [this message]
2017-08-15 10:03 ` Felipe Balbi
2017-08-15 11:51 ` Danilo Krummrich
2017-08-15 12:02 ` Felipe Balbi
2017-08-15 12:51 ` Danilo Krummrich
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=20170814163652.29108-1-danilokrummrich@dk-develop.de \
--to=danilokrummrich@dk-develop.de \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
Powered by JetHome