All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anton Danilov <littlesmilingcloud@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, 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, 08 Oct 2026 23:40:14 +0000	[thread overview]
Message-ID: <179150281451.481494.16961080980832187357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005191227.894665-1-littlesmilingcloud@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  5 Oct 2026 22:12:27 +0300 you 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.
> 
> [...]

Here is the summary with links:
  - [net] ip6_gre: let collect_md ip6gretap send from the unspecified address
    https://git.kernel.org/netdev/net-next/c/f3f5d7ab19b5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-08 23:40 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
2026-10-08 23:40 ` patchwork-bot+netdevbpf [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=179150281451.481494.16961080980832187357.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.