All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy L Tice <rtice@cisco.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, thomas@monjalon.net, pbhagavatula@marvell.com,
	sthotton@marvell.com, ndabilpuram@marvell.com,
	kirankumark@marvell.com, skori@marvell.com,
	skoteshwar@marvell.com, hkalra@marvell.com,
	rbhansali@marvell.com, Randy L Tice <rtice@cisco.com>
Subject: [PATCH 0/1] Fix CN20K mbuf size truncation
Date: Wed,  9 Sep 2026 12:06:36 -0400	[thread overview]
Message-ID: <20260909160637.3607104-1-rtice@cisco.com> (raw)

This small fix prepares the CN20K inline security receive paths for mbuf
layouts larger than 255 bytes.

The affected code recovers a packet mbuf by subtracting the size of
struct rte_mbuf from a pointer stored in completion metadata. Keeping
that size in an 8-bit local variable makes the recovery sensitive to
future mbuf layout growth. The patch widens the local size variable
without changing the surrounding fast-path logic.

The issue was found while preparing an unrelated mbuf layout extension.

Randy L Tice (1):
  drivers: fix CN20K mbuf size truncation

 .mailmap                          | 1 +
 drivers/event/cnxk/cn20k_worker.h | 4 ++--
 drivers/net/cnxk/cn20k_rx.h       | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.35.6

             reply	other threads:[~2026-09-09 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 16:06 Randy L Tice [this message]
2026-09-09 16:06 ` [PATCH 1/1] drivers: fix CN20K mbuf size truncation Randy L Tice
2026-09-09 17:16   ` Stephen Hemminger
2026-09-09 18:18     ` Morten Brørup
2026-09-09 20:42       ` Stephen Hemminger

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=20260909160637.3607104-1-rtice@cisco.com \
    --to=rtice@cisco.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=rbhansali@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stable@dpdk.org \
    --cc=sthotton@marvell.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.