From: David Miller <davem@davemloft.net>
To: jie.yang@atheros.com
Cc: miles.lane@gmail.com, chris.snook@gmail.com, jcliburn@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch net-next]atl1e:fix 2.6.31-git4 -- ATL1E 0000:03:00.0: DMA-API: device driver frees DMA
Date: Wed, 16 Sep 2009 00:44:52 -0700 (PDT) [thread overview]
Message-ID: <20090916.004452.40084897.davem@davemloft.net> (raw)
In-Reply-To: <12530857843502-git-send-email-jie.yang@atheros.com>
From: <jie.yang@atheros.com>
Date: Wed, 16 Sep 2009 15:23:04 +0800
> [ 25.059969] WARNING: at lib/dma-debug.c:816 check_unmap+0x383/0x55c()
> [ 25.059976] Hardware name: 1000HE
> [ 25.059984] ATL1E 0000:03:00.0: DMA-API: device driver frees DMA
> memory with wrong function [device address=0x0000000036b92802]
> [size=90 bytes] [mapped as single] [unmapped as page]
>
> use the wrong API when free dma. So when map dma use a flag to
> demostrate whether it is 'pci_map_single' or 'pci_map_page'. When free
> the dma, check the flags to select the right APIs('pci_unmap_single' or 'pci_unmap_page').
>
> set the flags type to u16 instead of unsigned long on David's comments.
>
> Signed-off-by: Jie Yang <jie.yang@atheros.com>
Your email client has corrupted this patch (turning tab characters
into spaces, etc.) making it unusable.
next prev parent reply other threads:[~2009-09-16 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:23 [Patch net-next]atl1e:fix 2.6.31-git4 -- ATL1E 0000:03:00.0: DMA-API: device driver frees DMA jie.yang
2009-09-16 7:44 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 9:28 jie.yang
2009-09-17 17:27 ` David Miller
2009-09-16 6:21 jie.yang
2009-09-16 6:57 ` David Miller
2009-09-16 9:10 ` Daniel Walker
2009-09-16 9:31 ` Jie Yang
2009-09-16 9:47 ` David Miller
2009-09-16 9:51 ` Cyrill Gorcunov
2009-09-16 9:54 ` Jie Yang
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=20090916.004452.40084897.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jie.yang@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=netdev@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).