From: Peter Chen <peter.chen@nxp.com>
To: balbi@kernel.org
Cc: linux-usb@vger.kernel.org, linux-imx@nxp.com,
Peter Chen <peter.chen@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: [PATCH 1/1] usb: gadget: core: wait gadget device .release finishing at usb_del_gadget_udc
Date: Fri, 31 Jul 2020 17:59:35 +0800 [thread overview]
Message-ID: <20200731095935.23034-1-peter.chen@nxp.com> (raw)
Per discussion[1], to avoid UDC driver possible freeing gadget device
memory before device core finishes using it, we add wait-complete
mechanism at usb_del_gadget_udc and gadget device .release callback.
After that, usb_del_gadget_udc will not return back until device
core finishes using gadget device.
For UDC drivers who have own .release callback, it needs to call
complete(&gadget->done) by themselves, if not, the UDC core will
handle it by default .release callback usb_gadget_release.
[1] https://www.spinics.net/lists/linux-usb/msg198790.html
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>
Suggested-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Peter Chen <peter.chen@nxp.com>
---
If this RFC patch is ok, I will create the formal patches which will change
UDC drivers who have their own .release function.
drivers/usb/gadget/udc/core.c | 14 +++++++++++---
include/linux/usb/gadget.h | 2 ++
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c
index ee226ad802a4..ed141e1a0dcf 100644
--- a/drivers/usb/gadget/udc/core.c
+++ b/drivers/usb/gadget/udc/core.c
@@ -1138,9 +1138,15 @@ static void usb_udc_release(struct device *dev)
static const struct attribute_group *usb_udc_attr_groups[];
-static void usb_udc_nop_release(struct device *dev)
+static void usb_gadget_release(struct device *dev)
{
+ struct usb_gadget *gadget;
+
dev_vdbg(dev, "%s\n", __func__);
+
+ gadget = container_of(dev, struct usb_gadget, dev);
+ complete(&gadget->done);
+ memset(dev, 0x0, sizeof(*dev));
}
/* should be called with udc_lock held */
@@ -1184,7 +1190,7 @@ int usb_add_gadget_udc_release(struct device *parent, struct usb_gadget *gadget,
if (release)
gadget->dev.release = release;
else
- gadget->dev.release = usb_udc_nop_release;
+ gadget->dev.release = usb_gadget_release;
device_initialize(&gadget->dev);
@@ -1324,6 +1330,7 @@ void usb_del_gadget_udc(struct usb_gadget *gadget)
dev_vdbg(gadget->dev.parent, "unregistering gadget\n");
mutex_lock(&udc_lock);
+ init_completion(&gadget->done);
list_del(&udc->list);
if (udc->driver) {
@@ -1338,7 +1345,8 @@ void usb_del_gadget_udc(struct usb_gadget *gadget)
flush_work(&gadget->work);
device_unregister(&udc->dev);
device_unregister(&gadget->dev);
- memset(&gadget->dev, 0x00, sizeof(gadget->dev));
+ /* Wait gadget release() is done */
+ wait_for_completion(&gadget->done);
}
EXPORT_SYMBOL_GPL(usb_del_gadget_udc);
diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
index 298b334e2951..ae346b524591 100644
--- a/include/linux/usb/gadget.h
+++ b/include/linux/usb/gadget.h
@@ -378,6 +378,7 @@ struct usb_gadget_ops {
* @lpm_capable: If the gadget max_speed is FULL or HIGH, this flag
* indicates that it supports LPM as per the LPM ECN & errata.
* @irq: the interrupt number for device controller.
+ * @done: gadget device's release() is done
*
* Gadgets have a mostly-portable "gadget driver" implementing device
* functions, handling all usb configurations and interfaces. Gadget
@@ -433,6 +434,7 @@ struct usb_gadget {
unsigned connected:1;
unsigned lpm_capable:1;
int irq;
+ struct completion done;
};
#define work_to_gadget(w) (container_of((w), struct usb_gadget, work))
--
2.17.1
next reply other threads:[~2020-07-31 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:59 Peter Chen [this message]
2020-07-31 11:55 ` [PATCH 1/1] usb: gadget: core: wait gadget device .release finishing at usb_del_gadget_udc Greg Kroah-Hartman
2020-07-31 12:11 ` Peter Chen
2020-07-31 12:25 ` Greg Kroah-Hartman
2020-07-31 14:06 ` Peter Chen
2020-07-31 14:12 ` Alan Stern
2020-07-31 23:42 ` Peter Chen
2020-08-01 6:53 ` Peter Chen
2020-08-01 7:04 ` Jun Li
2020-08-01 15:44 ` Alan Stern
2020-07-31 14:16 ` Greg Kroah-Hartman
2020-09-07 7:48 ` Felipe Balbi
2020-09-07 14:18 ` Alan Stern
2020-09-07 14:26 ` Felipe Balbi
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=20200731095935.23034-1-peter.chen@nxp.com \
--to=peter.chen@nxp.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).