All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, bluca@debian.org, dsahern@kernel.org,
	imer@imer.cc
Subject: Re: [PATCH iproute2] iptunnel: detect protocol mismatch on tunnel change
Date: Fri, 14 Apr 2023 20:10:18 +0000	[thread overview]
Message-ID: <168150301875.15322.4144586123529636419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410233509.7616-1-stephen@networkplumber.org>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Mon, 10 Apr 2023 16:35:09 -0700 you wrote:
> If attempt is made to change an IPv6 tunnel by using IPv4
> parameters, a stack overflow would happen and garbage request
> would be passed to kernel.
> 
> Example:
> ip tunnel add gre1 mode ip6gre local 2001:db8::1 remote 2001:db8::2 ttl 255
> ip tunnel change gre1 mode gre local 192.168.0.0 remote 192.168.0.1 ttl 255
> 
> [...]

Here is the summary with links:
  - [iproute2] iptunnel: detect protocol mismatch on tunnel change
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=8cc2eac60d5f

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



      parent reply	other threads:[~2023-04-14 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 23:35 [PATCH iproute2] iptunnel: detect protocol mismatch on tunnel change Stephen Hemminger
2023-04-11 10:09 ` Luca Boccassi
2023-04-11 15:55 ` David Ahern
2023-04-11 16:49   ` Stephen Hemminger
2023-04-14 20:10 ` 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=168150301875.15322.4144586123529636419.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bluca@debian.org \
    --cc=dsahern@kernel.org \
    --cc=imer@imer.cc \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 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.