All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Yaroslav Dudkov <aroslavdudkov622@gmail.com>
Cc: Laika Price <laikabcprice@gmail.com>,
	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>, Shuah Khan <shuah@kernel.org>,
	Stefano Brivio <sbrivio@redhat.com>,
	Guillaume Nault <gnault@redhat.com>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Aaron Conole <aconole@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v3] ip_tunnel: drop stale dst from generated PMTU ICMP replies
Date: Wed, 2 Sep 2026 14:39:18 +0300	[thread overview]
Message-ID: <20260902113918.GA3864622@shredder> (raw)
In-Reply-To: <20260901081825.287173-1-aroslavdudkov622@gmail.com>

On Tue, Sep 01, 2026 at 08:17:09AM +0000, Yaroslav Dudkov wrote:
> Since this series hasn't moved since June, and I've been debugging the
> same code path independently, sharing what I found in the hope it
> unblocks things. The kernel fix should of course remain Laika's;
> consider this supporting data.

I will send the kernel fix that I suggested and the selftest adjustment
as a single patch later today. Will add a Reported-by tag with your
name. Feel free to add a Tested-by tag later on.

Thanks

      reply	other threads:[~2026-09-02 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-13 23:13 [PATCH net v3] ip_tunnel: drop stale dst from generated PMTU ICMP replies Laika Price
2026-06-13 23:13 ` Laika Price via B4 Relay
2026-06-14  1:42 ` Jakub Kicinski
2026-06-16 11:02 ` Ido Schimmel
2026-09-01  8:17   ` Yaroslav Dudkov
2026-09-02 11:39     ` 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=20260902113918.GA3864622@shredder \
    --to=idosch@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=aroslavdudkov622@gmail.com \
    --cc=carnil@debian.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=laikabcprice@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbrivio@redhat.com \
    --cc=shuah@kernel.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.