Netdev List
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Anton Danilov <littlesmilingcloud@gmail.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, William Tu <u9012063@gmail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] ip6_gre: let collect_md ip6gretap send from the unspecified address
Date: Thu, 8 Oct 2026 17:14:20 +0300	[thread overview]
Message-ID: <20261008141420.GA1454005@shredder> (raw)
In-Reply-To: <20261005191227.894665-1-littlesmilingcloud@gmail.com>

On Mon, Oct 05, 2026 at 10:12:27PM +0300, Anton Danilov wrote:
> ip6gre_xmit_ipv6() drops an IPv6 packet whose source address equals the
> tunnel remote, to avoid a trivial tunneling loop. On a collect_md
> ip6gretap device t->parms.raddr is not the exit point: the outer
> destination comes from the per-packet tunnel metadata. Such devices are
> normally created without a remote, so raddr is ::, and the check never
> matches a real tunnel endpoint. It matches every frame sent from the
> unspecified address instead.
> 
> On an L2 tunnel those frames are regular link traffic. Duplicate Address
> Detection sends its Neighbor Solicitations from :: (RFC 4862, section
> 5.4.2), and MLD reports are sent from :: while an interface has no
> link-local address yet (RFC 3590, section 4). Frames bridged into a
> collect_md ip6gretap device, e.g. with tc tunnel_key and mirred, are
> dropped even though they carry valid metadata, so DAD cannot detect a
> duplicate address on the other side of the tunnel.
> 
> Skip the check for collect_md devices of type ARPHRD_ETHER. It stays for
> L3 ip6gre, where sending a packet with an unspecified source means
> forwarding it (RFC 4291, section 2.5.2), and for ip6gretap without
> collect_md. ip6erspan does not run this check in collect_md mode either.
> 
> Fixes: 6712abc168eb ("ip6_gre: add ip6 gre and gretap collect_md mode")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Anton Danilov <littlesmilingcloud@gmail.com>

AFAICT, this isn't a regression, so for net-next:

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

Jakub might agree to strip the tags before applying, so don't send v2
just yet. And if v2 is required, I would also drop the comment as it
simply repeats the commit message.

  parent reply	other threads:[~2026-10-08 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 19:12 [PATCH net] ip6_gre: let collect_md ip6gretap send from the unspecified address Anton Danilov
2026-10-05 19:20 ` netdev-bot+sinfo
2026-10-05 23:38   ` Anton Danilov
2026-10-08 14:14 ` Ido Schimmel [this message]
2026-10-08 23:40 ` patchwork-bot+netdevbpf

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=20261008141420.GA1454005@shredder \
    --to=idosch@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=littlesmilingcloud@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --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