mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Zhan <wang.zhan@smartx.com>
To: netdev@vger.kernel.org, Zihan Xi <zihanx@nebusec.ai>
Cc: Wang Zhan <wang.zhan@smartx.com>,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org,
	steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
	dsahern@kernel.org, idosch@nvidia.com, willemb@google.com,
	kuniyu@google.com, kees@kernel.org, richardbgobert@gmail.com,
	alice.kernel@fastmail.im, gal@nvidia.com,
	jibin.zhang@mediatek.com, luoxuanqiang@kylinos.cn,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Vega <vega@nebusec.ai>, Luxing Yin <root@tr0jan.top>
Subject: Re: [PATCH net v3 1/1] net: gso: limit recursive IP-in-IP segmentation
Date: Mon, 21 Sep 2026 12:29:07 +0800	[thread overview]
Message-ID: <20260921042907.3658794-1-wang.zhan@smartx.com> (raw)
In-Reply-To: <43510074c063f57e5738ecc55057e7fbbcdb1fbc.1789802623.git.zihanx@nebusec.ai>

On Sat, 19 Sep 2026 11:14:40 +0000 Zihan Xi wrote:
> @@ -19,10 +19,39 @@  struct skb_gso_cb {
>  	int	encap_level;
>  	__wsum	csum;
>  	__u16	csum_start;
> +	/* Bytes charged to the current GSO callback chain. */
> +	u16	gso_header_len;
>  };

Hi, I think skb_gso_cb->mac_offset already has enough information to tell
whether the budget is exceeded, so adding a field for it is unnecessary.

  reply	other threads:[~2026-09-21  4:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 11:14 [PATCH net v3 0/1] " Zihan Xi
2026-09-19 11:14 ` [PATCH net v3 1/1] " Zihan Xi
2026-09-21  4:29   ` Wang Zhan [this message]
2026-09-22  1:23   ` Willem de Bruijn

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=20260921042907.3658794-1-wang.zhan@smartx.com \
    --to=wang.zhan@smartx.com \
    --cc=alice.kernel@fastmail.im \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=jibin.zhang@mediatek.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoxuanqiang@kylinos.cn \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardbgobert@gmail.com \
    --cc=root@tr0jan.top \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=vega@nebusec.ai \
    --cc=willemb@google.com \
    --cc=zihanx@nebusec.ai \
    /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

all inboxes | Powered by JetHome®