DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wenbo Cao <caowenbo@mucse.com>
To: stephen@networkplumber.org
Cc: dev@dpdk.org, yaojun@mucse.com, Wenbo Cao <caowenbo@mucse.com>
Subject: [PATCH v2 0/3] [v2]drivers/net/rnp fixed Coverity issue
Date: Mon, 30 Jun 2025 13:57:50 +0800	[thread overview]
Message-ID: <20250630055753.35445-1-caowenbo@mucse.com> (raw)

This patchset primarily optimizes the robustness of code logic and
resolves anomalies in TSO segmentation.

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 (3):
  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

 drivers/net/rnp/base/rnp_mbx_fw.c |  15 +++-
 drivers/net/rnp/rnp_ethdev.c      |  16 ++--
 drivers/net/rnp/rnp_rxtx.c        | 118 +++++++++++++++++++++++-------
 drivers/net/rnp/rnp_rxtx.h        |   1 +
 4 files changed, 116 insertions(+), 34 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-06-30  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  5:57 Wenbo Cao [this message]
2025-06-30  5:57 ` [PATCH v2 1/3] net/rnp: add check firmware respond info Wenbo Cao
2025-06-30 15:07   ` Stephen Hemminger
2025-06-30  5:57 ` [PATCH v2 2/3] net/rnp: fix Tunnel-TSO VLAN header untrusted loop bound Wenbo Cao
2025-06-30  5:57 ` [PATCH v2 3/3] net/rnp: fix TSO segmentation for packets of 64KB Wenbo Cao

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=20250630055753.35445-1-caowenbo@mucse.com \
    --to=caowenbo@mucse.com \
    --cc=dev@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).