From: Bhagyada Modali <bhagyada.modali@amd.com>
To: <chandu@amd.com>, <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
Bhagyada Modali <bhagyada.modali@amd.com>
Subject: [PATCH v3 2/4] net/axgbe: fix mbuf lengths in scattered Rx
Date: Fri, 2 Sep 2022 04:47:52 -0400 [thread overview]
Message-ID: <20220902084754.99884-2-bhagyada.modali@amd.com> (raw)
In-Reply-To: <20220902084754.99884-1-bhagyada.modali@amd.com>
Updated pkt_len and data_len in the last segment of the packet.
Fixes: 965b3127d425 ("net/axgbe: support scattered Rx")
Cc: stable@dpdk.org
Signed-off-by: Bhagyada Modali <bhagyada.modali@amd.com>
---
drivers/net/axgbe/axgbe_rxtx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/axgbe/axgbe_rxtx.c b/drivers/net/axgbe/axgbe_rxtx.c
index 89ed6fd74a..2c2554e900 100644
--- a/drivers/net/axgbe/axgbe_rxtx.c
+++ b/drivers/net/axgbe/axgbe_rxtx.c
@@ -391,8 +391,8 @@ uint16_t eth_axgbe_recv_scattered_pkts(void *rx_queue,
} else {
eop = 1;
pkt_len = AXGMAC_GET_BITS_LE(desc->write.desc3,
- RX_NORMAL_DESC3, PL);
- data_len = pkt_len - rxq->crc_len;
+ RX_NORMAL_DESC3, PL) - rxq->crc_len;
+ data_len = pkt_len % rxq->buf_size;
/* Check for any errors and free mbuf*/
err = AXGMAC_GET_BITS_LE(desc->write.desc3,
RX_NORMAL_DESC3, ES);
--
2.25.1
next prev parent reply other threads:[~2022-09-02 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220901124948.97063-1-bhagyada.modali@amd.com>
2022-09-02 8:47 ` [PATCH v3 1/4] net/axgbe: fix " Bhagyada Modali
2022-09-02 8:47 ` Bhagyada Modali [this message]
2022-09-02 8:47 ` [PATCH v3 3/4] net/axgbe: fix length of each segment in " Bhagyada Modali
2022-09-02 8:47 ` [PATCH v3 4/4] net/axgbe: fix checksum and RSS " Bhagyada Modali
2022-09-05 5:00 ` [PATCH v3 1/4] net/axgbe: fix " Namburu, Chandu-babu
2022-09-05 16:48 ` 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=20220902084754.99884-2-bhagyada.modali@amd.com \
--to=bhagyada.modali@amd.com \
--cc=chandu@amd.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stable@dpdk.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).