linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: changbin.du@intel.com
To: balbi@ti.com
Cc: gregkh@linuxfoundation.org, John.Youn@synopsys.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, "Du,
	Changbin" <changbin.du@intel.com>
Subject: [PATCH] usb: gadget: forbid queuing request to a disabled ep
Date: Fri,  4 Dec 2015 15:21:16 +0800	[thread overview]
Message-ID: <1449213676-27334-1-git-send-email-changbin.du@intel.com> (raw)
In-Reply-To: <0C18FE92A7765D4EB9EE5D38D86A563A01DE83B2@SHSMSX103.ccr.corp.intel.com>

From: "Du, Changbin" <changbin.du@intel.com>

Queue a request to disabled ep  doesn't make sense, and induce caller
make mistakes.

Here is a example for the android mtp gadget function driver. A mem
corruption can happen on below senario.
1) On disconnect, mtp driver disable its EPs,
2) During send_file_work and receive_file_work, mtp queues a request
   to ep. (The mtp driver need improve its synchronization logic!)
3) mtp_function_unbind is invoked and all mtp requests are freed.
4) when udc process the request queued on step 2, will cause kernel
   NULL pointer dereference exception.

Signed-off-by: Du, Changbin <changbin.du@intel.com>
---
This patch is seprated from below patches because gadget layer has
added the 'enabled' flag in v4.4. so abandon it and submit new one.
[PATCH 0/2] Two fix for dwc2 gadget driver
  usb: dwc2: add ep enabled flag to avoid double enable/disable
  usb: dwc2: forbid queuing request to a disabled ep

---
 include/linux/usb/gadget.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
index 3d583a1..d813bd2 100644
--- a/include/linux/usb/gadget.h
+++ b/include/linux/usb/gadget.h
@@ -402,6 +402,9 @@ static inline void usb_ep_free_request(struct usb_ep *ep,
 static inline int usb_ep_queue(struct usb_ep *ep,
 			       struct usb_request *req, gfp_t gfp_flags)
 {
+	if (!ep->enabled)
+		return -ESHUTDOWN;
+
 	return ep->ops->queue(ep, req, gfp_flags);
 }
 
-- 
2.5.0


  reply	other threads:[~2015-12-04  7:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  5:21 [PATCH 0/2] Two fix for dwc2 gadget driver changbin.du
2015-11-30  5:21 ` [PATCH 1/2] usb: dwc2: add ep enabled flag to avoid double enable/disable changbin.du
2015-12-10 17:26   ` Felipe Balbi
2015-12-14  3:23     ` Du, Changbin
2015-11-30  5:21 ` [PATCH 2/2] usb: dwc2: forbid queuing request to a disabled ep changbin.du
2015-12-10 17:27   ` Felipe Balbi
2015-12-03  1:20 ` [PATCH 0/2] Two fix for dwc2 gadget driver John Youn
2015-12-03  4:23   ` Du, Changbin
2015-12-04  7:21     ` changbin.du [this message]
2015-12-10 17:28       ` [PATCH] usb: gadget: forbid queuing request to a disabled ep Felipe Balbi
2015-12-14  3:48         ` [PATCH v2] " changbin.du
2015-12-14 10:20           ` Du, Changbin
2015-12-16 16:52             ` Felipe Balbi
2015-12-17  9:35               ` Du, Changbin
2015-12-17 10:00               ` [PATCH v3] " changbin.du
2015-12-17 15:26                 ` Felipe Balbi
2015-12-18  7:34                   ` Du, Changbin
2015-12-18  7:36                   ` [PATCH v4] " changbin.du

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=1449213676-27334-1-git-send-email-changbin.du@intel.com \
    --to=changbin.du@intel.com \
    --cc=John.Youn@synopsys.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).