From: Govindarajulu Varadarajan <_govind@gmx.com>
To: davem@davemloft.net, netdev@vger.kernel.org, sassmann@redhat.com
Cc: ssujith@cisco.com, benve@cisco.com,
Govindarajulu Varadarajan <_govind@gmx.com>
Subject: [PATCH net-next 0/3] enic: Check for DMA mapping error
Date: Wed, 24 Dec 2014 15:59:35 +0530 [thread overview]
Message-ID: <1419416978-1008-1-git-send-email-_govind@gmx.com> (raw)
After dma mapping the buffers, enic does not call dma_mapping_error() to check
if mapping is successful.
This series fixes the issue by checking return value of pci_dma_mapping_error()
after pci_map_single().
This is reported by redhat here
https://bugzilla.redhat.com/show_bug.cgi?id=1145016
Govindarajulu Varadarajan (3):
enic: make vnic_wq_buf doubly linked
enic: check dma_mapping_error
enic: add stats for dma mapping error
drivers/net/ethernet/cisco/enic/enic.h | 14 +++
drivers/net/ethernet/cisco/enic/enic_ethtool.c | 19 +++-
drivers/net/ethernet/cisco/enic/enic_main.c | 152 +++++++++++++++----------
drivers/net/ethernet/cisco/enic/vnic_stats.h | 5 +
drivers/net/ethernet/cisco/enic/vnic_wq.c | 3 +
drivers/net/ethernet/cisco/enic/vnic_wq.h | 1 +
6 files changed, 135 insertions(+), 59 deletions(-)
--
2.2.1
next reply other threads:[~2014-12-24 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 10:29 Govindarajulu Varadarajan [this message]
2014-12-24 10:29 ` [PATCH net-next 1/3] enic: make vnic_wq_buf doubly linked Govindarajulu Varadarajan
2015-01-05 17:30 ` David Laight
2014-12-24 10:29 ` [PATCH net-next 2/3] enic: check dma_mapping_error Govindarajulu Varadarajan
2015-01-05 17:28 ` David Laight
2014-12-24 10:29 ` [PATCH net-next 3/3] enic: add stats for dma mapping error Govindarajulu Varadarajan
2014-12-31 18:09 ` [PATCH net-next 0/3] enic: Check for DMA " David Miller
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=1419416978-1008-1-git-send-email-_govind@gmx.com \
--to=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=ssujith@cisco.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).