From: Stephen Hemminger <stephen@networkplumber.org>
To: Wenbo Cao <caowenbo@mucse.com>
Cc: dev@dpdk.org, yaojun@mucse.com
Subject: Re: [PATCH v3 0/4] [v3]drivers/net/rnp fixed Coverity issue
Date: Thu, 16 Oct 2025 08:54:44 -0700 [thread overview]
Message-ID: <20251016085444.5dbe21ec@hermes.local> (raw)
In-Reply-To: <20251010070122.161401-1-caowenbo@mucse.com>
On Fri, 10 Oct 2025 15:01:18 +0800
Wenbo Cao <caowenbo@mucse.com> wrote:
> This patchset primarily optimizes the robustness of code logic and
> resolves anomalies in TSO segmentation.
>
> v3:
> * fixed no-lsc base api memory overflow.
> v2:
> * Optimized logical portability per Stephen Hemminger's suggestions
> v1:
> * fixed complie issue
> v0:
> *:fixed the below issue:
> Coverity issue: 468860,468866,468858
> Fixes: 4530e70f1e32 ("net/rnp: support Tx TSO offload")
> Fixes: 52dfb84e14be ("net/rnp: add device init and uninit")
> Fixes: 52aae4ed4ffb ("net/rnp: add device capabilities")
> *:fixed 64k tso
>
> Wenbo Cao (4):
> net/rnp: add check firmware respond info
> net/rnp: fix Tunnel-TSO VLAN header untrusted loop bound
> net/rnp: fix TSO segmentation for packets of 64KB
> net/rnp: resolve coredump caused by memory overflow
>
> drivers/net/rnp/base/rnp_mbx_fw.c | 19 ++++-
> drivers/net/rnp/rnp_ethdev.c | 16 ++--
> drivers/net/rnp/rnp_rxtx.c | 118 +++++++++++++++++++++++-------
> drivers/net/rnp/rnp_rxtx.h | 1 +
> 4 files changed, 118 insertions(+), 36 deletions(-)
>
Queued to next-net
prev parent reply other threads:[~2025-10-16 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:01 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 ` [PATCH v3 4/4] net/rnp: resolve coredump caused by memory overflow Wenbo Cao
2025-10-16 15:54 ` Stephen Hemminger [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=20251016085444.5dbe21ec@hermes.local \
--to=stephen@networkplumber.org \
--cc=caowenbo@mucse.com \
--cc=dev@dpdk.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).