mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vladimir Vdovin" <deliran@verdict.gg>
To: <netdev-bot+sinfo@kernel.org>, "Vladimir Vdovin" <deliran@verdict.gg>
Cc: "David Ahern" <dsahern@kernel.org>,
	"Ido Schimmel" <idosch@nvidia.com>,
	"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>,
	"Shuah Khan" <shuah@kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next v4 0/3] ipv4/ipv6: Cache pmtu on all paths of a multipath route
Date: Thu, 19 Nov 2026 16:32:38 +0300	[thread overview]
Message-ID: <DMZ84JBLQD08.3E6KHRQNK83FW@verdict.gg> (raw)
In-Reply-To: <179494427164.3291.6413261457824057937@kernel.org>

On Tue, Nov 17, 2026 at 07:37:51PM +0000, netdev-bot+sinfo wrote:
> Hi!
>
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
>
>  - How the issue was discovered, e.g. hit in production, hit during
>    development, syzbot report, manual code inspection, LLM or static
>    analysis tool scan.
>
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account.
>
> *IMPORTANT*: If you do repost (for other reasons) - please include
> the relevant info in the cover letter or commit messages.

Patch 2 fixes for IPv6 what commit 7d3f3b4367f3 fixed for IPv4, a
production issue back then, the cover letter links the discussion.
Patch 1 was found by code inspection while reworking v1 after the
Sashiko review of it.


      reply	other threads:[~2026-11-19 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 19:31 Vladimir Vdovin
2026-11-17 19:31 ` [PATCH net-next v4 1/3] ipv4: Check a Fragmentation Needed against each path " Vladimir Vdovin
2026-11-17 19:31 ` [PATCH net-next v4 2/3] ipv6: Cache pmtu for all paths " Vladimir Vdovin
2026-11-17 19:31 ` [PATCH net-next v4 3/3] selftests: net: pmtu: Add IPv6 and asymmetric multipath tests Vladimir Vdovin
2026-11-17 19:37 ` [PATCH net-next v4 0/3] ipv4/ipv6: Cache pmtu on all paths of a multipath route netdev-bot+sinfo
2026-11-19 13:32   ` Vladimir Vdovin [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=DMZ84JBLQD08.3E6KHRQNK83FW@verdict.gg \
    --to=deliran@verdict.gg \
    --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=linux-kselftest@vger.kernel.org \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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 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®