public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Mariusz Klimek <maklimek97@gmail.com>,
	netdev@vger.kernel.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH net-next v2 1/3] net: gso: do not include jumbogram HBH header in seglen calculation
Date: Tue, 13 Jan 2026 14:51:08 +0100	[thread overview]
Message-ID: <55e12beb-758c-4f82-992e-e07c9c300d4b@redhat.com> (raw)
In-Reply-To: <a9dcc27d-521e-44b0-b399-c353ef50077a@redhat.com>

On 1/13/26 9:40 AM, Paolo Abeni wrote:
> On 1/6/26 10:52 AM, Mariusz Klimek wrote:
>> @@ -177,8 +178,13 @@ static unsigned int skb_gso_transport_seglen(const struct sk_buff *skb)
>>   */
>>  static unsigned int skb_gso_network_seglen(const struct sk_buff *skb)
>>  {
>> -	unsigned int hdr_len = skb_transport_header(skb) -
>> -			       skb_network_header(skb);
>> +	unsigned int off = skb_network_offset(skb) + sizeof(struct ipv6hdr);
>> +	unsigned int hdr_len = skb_network_header_len(skb);
>> +
>> +	/* Jumbogram HBH header is removed upon segmentation. */
>> +	if (skb_protocol(skb, true) == htons(ETH_P_IPV6) &&
>> +	    skb->len - off > IPV6_MAXPLEN)
>> +		hdr_len -= sizeof(struct hop_jumbo_hdr);
> 
> IIRC there is some ongoing discussion about introducing big tcp support
> for virtio. Perhaps a DEBUG_NET_WARN_ON_ONCE(SKB_GSO_DODGY) could help
> keeping this check updated at due time?
> 
> @Jason: could you please double check if I'm off WRT virtio support for
> big TCP?

Reconsidering the above, I think the mentioned check could be added
separately, if and when virtio big TCP will come to life.

/P


  reply	other threads:[~2026-01-13 13:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  9:52 [PATCH net-next v2 0/3] net: gso: fix MTU validation of BIG TCP Mariusz Klimek
2026-01-06  9:52 ` [PATCH net-next v2 1/3] net: gso: do not include jumbogram HBH header in seglen calculation Mariusz Klimek
2026-01-13  8:40   ` Paolo Abeni
2026-01-13 13:51     ` Paolo Abeni [this message]
2026-01-14  3:47       ` Jason Wang
2026-01-13 14:14   ` Paolo Abeni
2026-01-14 15:52     ` Mariusz Klimek
2026-01-06  9:52 ` [PATCH net-next v2 2/3] ipv6: remove IP6SKB_FAKEJUMBO flag Mariusz Klimek
2026-01-06  9:52 ` [PATCH net-next v2 3/3] selftests/net: remove unnecessary MTU config in big_tcp.sh Mariusz Klimek
2026-01-13 21:42 ` [PATCH net-next v2 0/3] net: gso: fix MTU validation of BIG TCP Alice Mikityanska
2026-01-30  8:57   ` Mariusz Klimek
2026-01-30 18:02     ` Alice Mikityanska

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=55e12beb-758c-4f82-992e-e07c9c300d4b@redhat.com \
    --to=pabeni@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=maklimek97@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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