From: Larry Finger <Larry.Finger@lwfinger.net>
To: Paulius Zaleckas <paulius.zaleckas@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-wireless@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC] usb: Check results of dma_map_single
Date: Wed, 04 Nov 2009 08:06:25 -0600 [thread overview]
Message-ID: <4AF18A61.20909@lwfinger.net> (raw)
In-Reply-To: <4AF17884.5000200@gmail.com>
Paulius Zaleckas wrote:
> On 11/04/2009 07:48 AM, Larry Finger wrote:
>> At http://marc.info/?l=linux-wireless&m=125695331205062&w=2, a problem
>> with DMA buffer processing was corrected for the libertas driver. Because
>> routine usb_fill_bulk_urb() does not check that DMA is possible when
>> dma_map_single() is called, this condition was not detected until the
>> buffer
>> was unmapped. By this time memory corruption had occurred.
>>
>> The situation is fixed by testing the returned DMA address. If not a
>> legal
>> address, a WARN_ON(1) is executed to provide traceback and the error is
>> returned.
>>
>> Signed-off-by: Larry
>> Finger<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
>> ---
>>
>> Index: linux-2.6/drivers/usb/core/hcd.c
>> ===================================================================
>> --- linux-2.6.orig/drivers/usb/core/hcd.c
>> +++ linux-2.6/drivers/usb/core/hcd.c
>> @@ -1281,6 +1281,13 @@ static int map_urb_for_dma(struct usb_hc
>> urb->setup_packet,
>> sizeof(struct usb_ctrlrequest),
>> DMA_TO_DEVICE);
>> + ret = dma_mapping_error(hcd->self.controller,
>> + urb->setup_dma);
>> + /* warn if DMA mapping failed */
>> + if (ret) {
>> + WARN_ON(1);
>> + return ret;
>> + }
>
> First of all you forgot to add { } around everything under if statement.
>
> I don't think WARN_ON is needed...
> dma_mapping_error under most architectures return 0 or 1 so it would be
> better to make some real error value. EAGAIN seems to be proper error,
> since documentation says that driver should try again later.
>
> I would write this error handler like this:
>
> if (dma_mapping_error(hcd->self.controller, urb->setup_dma))
> ret = -EAGAIN;
>
>> else if (hcd->driver->flags& HCD_LOCAL_MEM)
>> ret = hcd_alloc_coherent(
>> urb->dev->bus, mem_flags,
>> @@ -1299,6 +1306,13 @@ static int map_urb_for_dma(struct usb_hc
>> urb->transfer_buffer,
>> urb->transfer_buffer_length,
>> dir);
>> + ret = dma_mapping_error(hcd->self.controller,
>> + urb->transfer_dma);
>> + /* warn if DMA mapping failed */
>> + if (ret) {
>> + WARN_ON(1);
>> + return ret;
>> + }
>
> ditto
>
>> else if (hcd->driver->flags& HCD_LOCAL_MEM) {
>> ret = hcd_alloc_coherent(
>> urb->dev->bus, mem_flags,
>
Thank you for your review and comments. I'll wait a bit to see what
other comments are offered, but I have implemented all your changes.
Larry
next prev parent reply other threads:[~2009-11-04 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 5:48 [RFC] usb: Check results of dma_map_single Larry Finger
2009-11-04 12:50 ` Paulius Zaleckas
2009-11-04 14:06 ` Larry Finger [this message]
2009-11-04 14:51 ` Michael Buesch
2009-11-04 15:16 ` Larry Finger
2009-11-04 19:49 ` Christian Lamparter
2009-11-05 2:41 ` Larry Finger
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=4AF18A61.20909@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gregkh@suse.de \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=paulius.zaleckas@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.