mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, William Tu <u9012063@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] ip6_gre: remove obsolete ERSPAN PMTU update
Date: Sun, 4 Oct 2026 10:27:07 +0300	[thread overview]
Message-ID: <20261004072707.GA72754@shredder> (raw)
In-Reply-To: <20261002033058.358137-1-4ncienth@gmail.com>

On Fri, Oct 02, 2026 at 12:30:58PM +0900, Daehyeon Ko wrote:
> A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb,
> and mirred can redirect it to a native ip6erspan device. The legacy PMTU
> update in ip6erspan_tunnel_xmit() treats that metadata dst as a route.
> Since it has no output device, dst_dev(dst)->mtu dereferences NULL.
> 
> On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used
> self-created user and network namespaces to trigger:
> 
>   KASAN: null-ptr-deref
>   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0
>   Kernel panic - not syncing: Fatal exception in interrupt
> 
> The update is obsolete. Commit fe1a4ca0a2b7 ("ip6_gre: process toobig
> in a better way") changed IPv6 GRE Too Big handling to update the
> underlay route and removed the equivalent block from __gre6_xmit().
> ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.
> 
> Remove the stale ERSPAN copy and its now-unused dst variable. This
> eliminates the metadata-dst dereference and keeps ERSPAN aligned with
> IPv6 GRE PMTU handling.
> 
> Fixes: 5a963eb61b7c ("ip6_gre: Add ERSPAN native tunnel support")
> Cc: stable@vger.kernel.org
> Suggested-by: Ido Schimmel <idosch@nvidia.com>
> Assisted-by: LLM
> Signed-off-by: Daehyeon Ko <4ncienth@gmail.com>

Reviewed-by: Ido Schimmel <idosch@nvidia.com>

      reply	other threads:[~2026-10-04  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  3:30 Daehyeon Ko
2026-10-04  7:27 ` Ido Schimmel [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=20261004072707.GA72754@shredder \
    --to=idosch@nvidia.com \
    --cc=4ncienth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=u9012063@gmail.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®