All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junfeng Guo <junfeng.guo@intel.com>
To: qi.z.zhang@intel.com, qiming.yang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org, ting.xu@intel.com,
	Junfeng Guo <junfeng.guo@intel.com>
Subject: [PATCH 0/2] fix variable type in pattern parsing for raw flow
Date: Thu, 15 Jun 2023 13:17:15 +0800	[thread overview]
Message-ID: <20230615051717.2906443-1-junfeng.guo@intel.com> (raw)

In current pattern parsing function for protocol agnostic flow
offloading (raw flow), some of the variables of packet length are
defined as uint8_t, which are too small for some large-size packets,
such as srv6 (Segment Routing over IPv6 dataplane) type. Change the
type to uint16_t.

For example, the length of below srv6 paket is 268 B, larger than the
max of uint8_t type (i.e., 256).
"mac()/ipv6(nextheader=43)/ipv6srh(headerextlength=4,nextheader=41)\
		/ipv6(dst=2001:2:0:0:0:0:0:2)"

Junfeng Guo (2):
  net/ice: fix variable type in pattern parsing for raw flow
  net/iavf: fix variable type in pattern parsing for raw flow

 drivers/net/iavf/iavf_hash.c      | 2 +-
 drivers/net/ice/ice_fdir_filter.c | 2 +-
 drivers/net/ice/ice_hash.c        | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-06-15  5:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  5:17 Junfeng Guo [this message]
2023-06-15  5:17 ` [PATCH 1/2] net/ice: fix variable type in pattern parsing for raw flow Junfeng Guo
2023-06-15  5:17 ` [PATCH 2/2] net/iavf: " Junfeng Guo
2023-06-15  5:23 ` [PATCH 0/2] " Xu, Ting
2023-06-15  7:28 ` David Marchand
2023-06-16  5:48   ` Zhang, Qi Z
2023-06-16  6:22     ` Guo, Junfeng
2023-06-19  0:57       ` Zhang, Qi Z

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=20230615051717.2906443-1-junfeng.guo@intel.com \
    --to=junfeng.guo@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=ting.xu@intel.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 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.