From: Shay Agroskin <shayagr@amazon.com>
To: <kuba@kernel.org>, <netdev@vger.kernel.org>
Cc: Shay Agroskin <shayagr@amazon.com>, <dwmw@amazon.com>,
<zorik@amazon.com>, <matua@amazon.com>, <saeedb@amazon.com>,
<msw@amazon.com>, <aliguori@amazon.com>, <nafea@amazon.com>,
<gtzalik@amazon.com>, <netanel@amazon.com>, <alisaidi@amazon.com>,
<benh@amazon.com>, <akiyano@amazon.com>, <sameehj@amazon.com>,
<ndagan@amazon.com>
Subject: [PATCH V2 net 0/4] Fixes for ENA driver
Date: Thu, 19 Nov 2020 22:28:47 +0200 [thread overview]
Message-ID: <20201119202851.28077-1-shayagr@amazon.com> (raw)
Hi all,
This series fixes some issues in the ENA driver:
- fix wrong data offset on machines that support rx offset
- work-around Intel iommu issue
- fix out of bound access when request id is wrong
- return error code if XDP TX xmit fails
Changes from previous version:
v1->v2: switched to using dma_set_mask_and_coherent() function
in second patch
Shay Agroskin (4):
net: ena: handle bad request id in ena_netdev
net: ena: set initial DMA width to avoid intel iommu issue
net: ena: fix packet's addresses for rx_offset feature
net: ena: return error code from ena_xdp_xmit_buff
drivers/net/ethernet/amazon/ena/ena_eth_com.c | 3 +
drivers/net/ethernet/amazon/ena/ena_netdev.c | 86 +++++++------------
2 files changed, 36 insertions(+), 53 deletions(-)
--
2.17.1
next reply other threads:[~2020-11-19 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 20:28 Shay Agroskin [this message]
2020-11-19 20:28 ` [PATCH V2 net 1/4] net: ena: handle bad request id in ena_netdev Shay Agroskin
2020-11-19 20:28 ` [PATCH V2 net 2/4] net: ena: set initial DMA width to avoid intel iommu issue Shay Agroskin
2020-11-19 20:28 ` [PATCH V2 net 3/4] net: ena: fix packet's addresses for rx_offset feature Shay Agroskin
2020-11-19 20:28 ` [PATCH V2 net 4/4] net: ena: return error code from ena_xdp_xmit_buff Shay Agroskin
2020-11-21 23:53 ` Jakub Kicinski
2020-11-22 7:19 ` Shay Agroskin
2020-11-23 16:18 ` Jakub Kicinski
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=20201119202851.28077-1-shayagr@amazon.com \
--to=shayagr@amazon.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=dwmw@amazon.com \
--cc=gtzalik@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=sameehj@amazon.com \
--cc=zorik@amazon.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).