From: Wenbo Cao <caowenbo@mucse.com>
To: stephen@networkplumber.org, Wenbo Cao <caowenbo@mucse.com>,
Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, yaojun@mucse.com, stable@dpdk.org
Subject: [PATCH v3 4/4] net/rnp: resolve coredump caused by memory overflow
Date: Fri, 10 Oct 2025 15:01:22 +0800 [thread overview]
Message-ID: <20251010070122.161401-5-caowenbo@mucse.com> (raw)
In-Reply-To: <20251010070122.161401-1-caowenbo@mucse.com>
Fix memory overflow issue running with --no-lsc-interrupt
when link update.
Fixes: 52dfb84e14be ("net/rnp: add device init and uninit")
Cc: stable@dpdk.org
Signed-off-by: Wenbo Cao <caowenbo@mucse.com>
---
drivers/net/rnp/base/rnp_mbx_fw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/rnp/base/rnp_mbx_fw.c b/drivers/net/rnp/base/rnp_mbx_fw.c
index 7ae8763a4a..307323b3d1 100644
--- a/drivers/net/rnp/base/rnp_mbx_fw.c
+++ b/drivers/net/rnp/base/rnp_mbx_fw.c
@@ -174,7 +174,7 @@ rnp_fw_send_cmd(struct rnp_eth_port *port,
if (err)
return err;
if (respond)
- memcpy(respond, cookie->priv, sizeof(cookie->priv));
+ memcpy(respond, cookie->priv, RNP_FW_REP_DATA_NUM);
} else {
rnp_build_fwcmd_req(&req, arg, &req);
err = rnp_fw_send_cmd_wait(port, &req, &reply);
--
2.34.1
prev parent reply other threads:[~2025-10-10 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:01 [PATCH v3 0/4] [v3]drivers/net/rnp fixed Coverity issue Wenbo Cao
2025-10-10 7:01 ` [PATCH v3 1/4] net/rnp: add check firmware respond info Wenbo Cao
2025-10-10 7:01 ` [PATCH v3 2/4] net/rnp: fix Tunnel-TSO VLAN header untrusted loop bound Wenbo Cao
2025-10-10 7:01 ` [PATCH v3 3/4] net/rnp: fix TSO segmentation for packets of 64KB Wenbo Cao
2025-10-10 7:01 ` Wenbo Cao [this message]
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=20251010070122.161401-5-caowenbo@mucse.com \
--to=caowenbo@mucse.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=yaojun@mucse.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).