From: "Wu, Songjun" <songjun.wu@atmel.com>
To: <balbi@ti.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <nicolas.ferre@atmel.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] USB: gadget: udc: atmel: fix possible oops when unloading module
Date: Wed, 24 Dec 2014 09:14:53 +0800 [thread overview]
Message-ID: <549A138D.50204@atmel.com> (raw)
In-Reply-To: <20141223162419.GB9147@saruman>
在 12/24/2014 00:24, Felipe Balbi 写道:
> On Mon, Dec 22, 2014 at 05:26:14PM +0800, Songjun Wu wrote:
>> When unloading the module, the urb request will be dequeued
>> and the completion routine will be excuted.
>> If no urb packet, the urb request will not be added to the endpoint queue
>> and the completion routine pointer in urb request is NULL.
>> Accessing to the NULL function pointer will cause the oops issue.
>> Add the code to check the urb request is in the endpoint queue or not.
>> If the urb request is not in the endpoint queue, a negative error code
>> will be returned.
>
> have you triggered the NULL pointer oops ? Care to add it to the commit
> log.
Executing the 'insmod g_hid.ko', then executing the 'rmmod g_hid.ko',
the NULL pointer oops will be triggered.
>
> Also, which commit is this fixing ? Does this need to be backported ?
> When was the bug introduced ?
>
>> Signed-off-by: Songjun Wu <songjun.wu@atmel.com>
>> ---
>> drivers/usb/gadget/udc/atmel_usba_udc.c | 12 +++++++++++-
>> 1 file changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/usb/gadget/udc/atmel_usba_udc.c b/drivers/usb/gadget/udc/atmel_usba_udc.c
>> index ce88237..48629cc 100644
>> --- a/drivers/usb/gadget/udc/atmel_usba_udc.c
>> +++ b/drivers/usb/gadget/udc/atmel_usba_udc.c
>> @@ -828,7 +828,7 @@ static int usba_ep_dequeue(struct usb_ep *_ep, struct usb_request *_req)
>> {
>> struct usba_ep *ep = to_usba_ep(_ep);
>> struct usba_udc *udc = ep->udc;
>> - struct usba_request *req = to_usba_req(_req);
>> + struct usba_request *req;
>> unsigned long flags;
>> u32 status;
>>
>> @@ -837,6 +837,16 @@ static int usba_ep_dequeue(struct usb_ep *_ep, struct usb_request *_req)
>>
>> spin_lock_irqsave(&udc->lock, flags);
>>
>> + list_for_each_entry(req, &ep->queue, queue) {
>> + if (&req->req == _req)
>> + break;
>> + }
>> +
>> + if (&req->req != _req) {
>> + spin_unlock_irqrestore(&udc->lock, flags);
>> + return -EINVAL;
>> + }
>> +
>> if (req->using_dma) {
>> /*
>> * If this request is currently being transferred,
>> --
>> 1.7.9.5
>>
>
next prev parent reply other threads:[~2014-12-24 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 9:26 [PATCH] USB: gadget: udc: atmel: fix possible oops when unloading module Songjun Wu
2014-12-23 16:24 ` Felipe Balbi
2014-12-24 1:14 ` Wu, Songjun [this message]
2014-12-26 15:27 ` Felipe Balbi
2014-12-29 9:15 ` 看看这样回复可以吗? " Wu, Songjun
2014-12-29 9:37 ` Wu, Songjun
2014-12-29 9:42 ` Wu, Songjun
2014-12-29 15:54 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 9:49 Songjun Wu
2015-01-08 17:15 ` 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=549A138D.50204@atmel.com \
--to=songjun.wu@atmel.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@atmel.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