All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, amcohen@nvidia.com, roopa@nvidia.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] ipv4/ipv6: do not warn on route notification size races
Date: Thu, 08 Oct 2026 18:50:07 +0000	[thread overview]
Message-ID: <179148540727.391001.3522675420264250688.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1791423190.git.4ncienth@gmail.com>

Hello:

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

On Thu,  8 Oct 2026 14:29:21 +0900 you wrote:
> A nexthop group can grow between route notification sizing and filling.
> Both IPv4 and IPv6 can then legitimately return -EMSGSIZE, so remove the
> stale warnings while preserving their existing error paths.
> 
> Patch 1 is unchanged from v1.  Patch 2 adds the IPv6 counterpart requested
> by Ido.  No new build or runtime test was run; both changes only delete the
> stale comment and WARN_ON().
> 
> [...]

Here is the summary with links:
  - [net,v2,1/2] ipv4: do not warn on route notification size race
    https://git.kernel.org/netdev/net/c/e02a5b658816
  - [net,v2,2/2] ipv6: do not warn on route notification size race
    https://git.kernel.org/netdev/net/c/c97426ec649d

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 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  5:29 [PATCH net v2 0/2] ipv4/ipv6: do not warn on route notification size races Daehyeon Ko
2026-10-08  5:29 ` [PATCH net v2 1/2] ipv4: do not warn on route notification size race Daehyeon Ko
2026-10-08  5:29 ` [PATCH net v2 2/2] ipv6: " Daehyeon Ko
2026-10-08  5:35 ` [PATCH net v2 0/2] ipv4/ipv6: do not warn on route notification size races netdev-bot+sinfo
2026-10-08 18:50 ` 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=179148540727.391001.3522675420264250688.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=4ncienth@gmail.com \
    --cc=amcohen@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roopa@nvidia.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.