From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Long Wu <long.wu@corigine.com>,
Chaoyong He <chaoyong.he@corigine.com>,
Peng Zhang <peng.zhang@corigine.com>
Subject: [PATCH 2/2] net/nfp: fix AVX2 vector Rx function memory overrun
Date: Wed, 17 Jul 2024 11:24:45 +0800 [thread overview]
Message-ID: <20240717032445.442348-3-chaoyong.he@corigine.com> (raw)
In-Reply-To: <20240717032445.442348-1-chaoyong.he@corigine.com>
From: Long Wu <long.wu@corigine.com>
CI found that the 'rxb' in 'nfp_net_vec_avx2_recv_pkts()' may
cause memory overrun.
Coverity issue:439964
Fixes: b67555307628 ("net/nfp: add AVX2 Rx")
Signed-off-by: Long Wu <long.wu@corigine.com>
Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
---
drivers/net/nfp/nfp_rxtx_vec_avx2.c | 41 ++++++++++++++++++-----------
1 file changed, 25 insertions(+), 16 deletions(-)
diff --git a/drivers/net/nfp/nfp_rxtx_vec_avx2.c b/drivers/net/nfp/nfp_rxtx_vec_avx2.c
index 508ec7faa5..2a033133a1 100644
--- a/drivers/net/nfp/nfp_rxtx_vec_avx2.c
+++ b/drivers/net/nfp/nfp_rxtx_vec_avx2.c
@@ -117,29 +117,48 @@ nfp_vec_avx2_recv_set_rxpkt1(struct nfp_net_rxq *rxq,
nfp_net_rx_cksum(rxq, rxds, rx_pkt);
}
-static inline void
+static inline int
nfp_vec_avx2_recv1(struct nfp_net_rxq *rxq,
struct nfp_net_rx_desc *rxds,
- struct rte_mbuf *rxb,
+ struct rte_mbuf **rxb,
struct rte_mbuf *rx_pkt)
{
+ /* Allocate a new mbuf into the software ring. */
+ if (rte_pktmbuf_alloc_bulk(rxq->mem_pool, rxb, 1) < 0) {
+ PMD_RX_LOG(DEBUG, "RX mbuf alloc failed port_id=%u queue_id=%hu",
+ rxq->port_id, rxq->qidx);
+ nfp_net_mbuf_alloc_failed(rxq);
+ return -ENOMEM;
+ }
+
nfp_vec_avx2_recv_set_rxpkt1(rxq, rxds, rx_pkt);
- nfp_vec_avx2_recv_set_des1(rxq, rxds, rxb);
+ nfp_vec_avx2_recv_set_des1(rxq, rxds, *rxb);
+
+ return 0;
}
-static inline void
+static inline int
nfp_vec_avx2_recv4(struct nfp_net_rxq *rxq,
struct nfp_net_rx_desc *rxds,
struct rte_mbuf **rxb,
struct rte_mbuf **rx_pkts)
{
+ /* Allocate 4 new mbufs into the software ring. */
+ if (rte_pktmbuf_alloc_bulk(rxq->mem_pool, rxb, 4) < 0) {
+ PMD_RX_LOG(DEBUG, "RX mbuf bulk alloc failed port_id=%u queue_id=%hu",
+ rxq->port_id, rxq->qidx);
+ return -ENOMEM;
+ }
+
nfp_vec_avx2_recv_set_rxpkt1(rxq, rxds, rx_pkts[0]);
nfp_vec_avx2_recv_set_rxpkt1(rxq, rxds + 1, rx_pkts[1]);
nfp_vec_avx2_recv_set_rxpkt1(rxq, rxds + 2, rx_pkts[2]);
nfp_vec_avx2_recv_set_rxpkt1(rxq, rxds + 3, rx_pkts[3]);
nfp_vec_avx2_recv_set_des4(rxq, rxds, rxb);
+
+ return 0;
}
static inline bool
@@ -215,15 +234,8 @@ nfp_net_vec_avx2_recv_pkts(void *rx_queue,
_mm_storel_epi64((void *)&rx_pkts[avail],
_mm_loadu_si128((void *)rxb));
- /* Allocate a new mbuf into the software ring. */
- if (rte_pktmbuf_alloc_bulk(rxq->mem_pool, rxb, 1) < 0) {
- PMD_RX_LOG(DEBUG, "RX mbuf alloc failed port_id=%u queue_id=%hu",
- rxq->port_id, rxq->qidx);
- nfp_net_mbuf_alloc_failed(rxq);
+ if (nfp_vec_avx2_recv1(rxq, rxds, rxb, rx_pkts[avail]) != 0)
goto recv_end;
- }
-
- nfp_vec_avx2_recv1(rxq, rxds, *rxb, rx_pkts[avail]);
avail++;
nb_hold++;
@@ -237,14 +249,11 @@ nfp_net_vec_avx2_recv_pkts(void *rx_queue,
_mm256_storeu_si256((void *)&rx_pkts[avail],
_mm256_loadu_si256((void *)rxb));
- /* Allocate 4 new mbufs into the software ring. */
- if (rte_pktmbuf_alloc_bulk(rxq->mem_pool, rxb, 4) < 0) {
+ if (nfp_vec_avx2_recv4(rxq, rxds, rxb, &rx_pkts[avail]) != 0) {
burst_receive = false;
continue;
}
- nfp_vec_avx2_recv4(rxq, rxds, rxb, &rx_pkts[avail]);
-
avail += 4;
nb_hold += 4;
}
--
2.39.1
next prev parent reply other threads:[~2024-07-17 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 3:24 [PATCH 0/2] fix coverity issues Chaoyong He
2024-07-17 3:24 ` [PATCH 1/2] net/nfp: fix copy and paste error Chaoyong He
2024-07-17 3:24 ` Chaoyong He [this message]
2024-07-19 7:40 ` [PATCH 0/2] fix coverity issues Ferruh Yigit
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=20240717032445.442348-3-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.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).