From: Christian Lamparter <chunkeey@googlemail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH V2] p54usb: Remove DMA buffer from stack
Date: Thu, 12 Nov 2009 10:51:11 +0100 [thread overview]
Message-ID: <200911121051.11982.chunkeey@googlemail.com> (raw)
In-Reply-To: <4afb5095.fKs+0FCQC9sTYyFW%Larry.Finger@lwfinger.net>
On Thursday 12 November 2009 01:02:29 Larry Finger wrote:
> On 2.6.32-rc6 from wireless-testing, the following warning is emitted:
>
> ------------[ cut here ]------------
> WARNING: at lib/dma-debug.c:860 check_for_stack+0xaa/0xe0()
> Hardware name: HP Pavilion dv2700 Notebook PC
> ehci_hcd 0000:00:02.1: DMA-API: device driver maps memory fromstack
> [addr=ffff8800b6e2bca8]
> Modules linked in: <Removed>
> Pid: 16378, comm: modprobe Not tainted 2.6.32-rc6-wl #244
> Call Trace:
> [<ffffffff81049698>] warn_slowpath_common+0x78/0xb0
> [<ffffffff8104972c>] warn_slowpath_fmt+0x3c/0x40
> [<ffffffff811ae52a>] check_for_stack+0xaa/0xe0
> [<ffffffff811afc8d>] debug_dma_map_page+0xfd/0x170
> [<ffffffffa006297a>] usb_hcd_submit_urb+0x3da/0x9c0 [usbcore]
> [<ffffffff81076e6f>] ? lockdep_init_map+0x5f/0x5d0
> [<ffffffffa0063365>] usb_submit_urb+0xe5/0x260 [usbcore]
> [<ffffffffa0064b7e>] usb_start_wait_urb+0x5e/0xf0 [usbcore]
> [<ffffffffa0063943>] ? usb_init_urb+0x23/0x40 [usbcore]
> [<ffffffffa0064cd4>] usb_bulk_msg+0xc4/0x150 [usbcore]
> [<ffffffffa0441a91>] T.719+0x31/0x40 [p54usb]
> [<ffffffffa0441acf>] p54u_upload_firmware_3887+0x2f/0x490 [p54usb]
> [<ffffffffa049c667>] ? p54_parse_firmware+0x427/0x450 [p54common]
> <Rest of traceback removed>
> ---[ end trace f77df0316ddad3de ]---
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.org>
> ---
>
> John,
>
> This is 2.6.32 material. Sorry to find it so late in the rc cycle. I hop
> DaveM doesn't give you too much trouble.
>
> V2 - Fix line wraps in trace back.
>
> Larry
> ---
>
> Index: wireless-testing/drivers/net/wireless/p54/p54usb.c
> ===================================================================
> --- wireless-testing.orig/drivers/net/wireless/p54/p54usb.c
> +++ wireless-testing/drivers/net/wireless/p54/p54usb.c
> @@ -426,12 +426,16 @@ static const char p54u_romboot_3887[] =
> static int p54u_firmware_reset_3887(struct ieee80211_hw *dev)
> {
> struct p54u_priv *priv = dev->priv;
> - u8 buf[4];
> + u8 *buf;
> int ret;
>
> - memcpy(&buf, p54u_romboot_3887, sizeof(buf));
> + buf = kmalloc(4, GFP_KERNEL);
> + if (!buf)
> + return -ENOMEM;
> + memcpy(buf, p54u_romboot_3887, 4);
> ret = p54u_bulk_msg(priv, P54U_PIPE_DATA,
> - buf, sizeof(buf));
> + buf, 4);
> + kfree(buf);
> if (ret)
> dev_err(&priv->udev->dev, "(p54usb) unable to jump to "
> "boot ROM (%d)!\n", ret);
>
Acked-by: Christian Lamparter <chunkeey@googlemail.com>
FYI, p54u_upload_firmware_net2280 will likely produce the same
same WARN, since "__le32 reg;" is held on the stack as well.
Regards,
Chr
next prev parent reply other threads:[~2009-11-12 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 0:02 [PATCH V2] p54usb: Remove DMA buffer from stack Larry Finger
2009-11-12 9:51 ` Christian Lamparter [this message]
2009-11-12 16:27 ` 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=200911121051.11982.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).