From: Ben Hutchings <bhutchings@solarflare.com>
To: Fugang Duan <B38611@freescale.com>
Cc: <b20596@freescale.com>, <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] net:fec: fix WARNING caused by lack of calls to dma_mapping_error()
Date: Wed, 13 Nov 2013 01:43:09 +0000 [thread overview]
Message-ID: <1384306989.3802.71.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <1384304453.3802.62.camel@bwh-desktop.uk.level5networks.com>
On Wed, 2013-11-13 at 01:00 +0000, Ben Hutchings wrote:
> On Tue, 2013-11-12 at 10:54 +0800, Fugang Duan wrote:
> > Enable CONFIG_HAVE_DMA_API_DEBUG, the kernel dump warning:
[...]
> > @@ -1001,6 +1005,9 @@ fec_enet_rx(struct net_device *ndev, int budget)
> >
> > bdp->cbd_bufaddr = dma_map_single(&fep->pdev->dev, data,
> > FEC_ENET_TX_FRSIZE, DMA_FROM_DEVICE);
> > + /* here dma mapping shouldn't be error, just avoid kernel dump */
> > + if (dma_mapping_error(&fep->pdev->dev, bdp->cbd_bufaddr))
> > + netdev_err(ndev, "Rx DMA memory map failed\n");
>
> This is not handling the error.
[...]
It looks like the same RX DMA buffers are used repeatedly and the driver
copies into an skb. So fec_enet_rx() should not map or unmap at all; it
should use dma_sync_single_for_cpu(). Then, indeed, no error handling
is required.
But there's still a big problem with this function. Instead of
remembering the virtual address of each buffer, it passes the DMA
address to __va(). Physical and DMA addresses are *not* the same thing!
They may differ if the device is behind an IOMMU or bounce buffering was
required, or just because there is a fixed offset between the device and
host physical addresses.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-11-13 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:54 [PATCH] net:fec: fix WARNING caused by lack of calls to dma_mapping_error() Fugang Duan
2013-11-13 1:00 ` Ben Hutchings
2013-11-13 1:43 ` Ben Hutchings [this message]
2013-11-13 2:10 ` Fugang Duan
2013-11-13 3:02 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2013-11-14 1:30 Fugang Duan
2013-11-14 2:12 ` Ben Hutchings
2013-11-14 2:15 ` Fugang Duan
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=1384306989.3802.71.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=B38611@freescale.com \
--cc=b20596@freescale.com \
--cc=davem@davemloft.net \
--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