mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Omar Ramadan <omar@blockcast.net>
To: Eric Dumazet <edumazet@kernel.org>
Cc: netdev-bot+sinfo@kernel.org, Taehee Yoo <ap420073@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] amt: do not offer software GSO on the amt device
Date: Thu,  1 Oct 2026 15:51:36 +0300	[thread overview]
Message-ID: <20261001125139.17059-1-omar@blockcast.net> (raw)
In-Reply-To: <CAL4Wiiqw_7Mxa5W1EQgw2=KpJNNxG=cBLXsHvpio29GvD1UKZg@mail.gmail.com>

(Resending with the list and Cc's restored; my first copy went to
Eric only by mistake.)

On Thu, Oct 1, 2026, Eric Dumazet wrote:
> 1)  Note that tx checksum offload is off by default on amt, so the bug
> would not trigger by default.

You're right, and I should have checked that before sending. With
tx-checksum-ip-generic off, netdev_fix_features() drops GSO_UDP_L4
from amt's features, so validate_xmit_skb() segments any UDP GSO skb
before amt_dev_xmit() sees it. It takes "ethtool -K <amt> tx on" first.

The commit message, and my reply to the bot, also overstate the
symptom. Even with tx on, the per-tunnel copy keeps csum_start on the
inner UDP header, so where it is segmented in software,
__udp_gso_segment() rejects it and the copy is dropped, rather than
being cut into malformed AMT messages. That is from reading the code,
not from a reproducer.

> 2) Please take a look at Documentation/process/coding-assistants.rst

Thanks, I have. Anything further I send that an LLM helped with will
carry an Assisted-by: tag and say what was and was not reproduced.

> 3) A better fix would be (for net-next) to call udp_tunnel_handle_offloads()
> in amt_send_multicast_data() like other UDP tunnels do

Agreed, please drop this patch. I'll do it that way for net-next,
with an amt.sh case that sends a UDP_SEGMENT burst through the relay
with tx on.

pw-bot: cr

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 18:15 Omar Ramadan
2026-09-28 18:19 ` netdev-bot+sinfo
2026-09-30 22:26   ` Omar Ramadan
2026-10-01  7:05     ` Eric Dumazet
2026-10-01 12:51       ` Omar Ramadan [this message]

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=20261001125139.17059-1-omar@blockcast.net \
    --to=omar@blockcast.net \
    --cc=andrew+netdev@lunn.ch \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®