From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
idosch@nvidia.com, kuniyu@google.com, leitao@debian.org,
aroulin@nvidia.com, fruggeri@arista.com,
stephen@networkplumber.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next v2 0/8] net: neighbour: Notify changes atomically
Date: Sun, 25 Jan 2026 23:00:14 +0000 [thread overview]
Message-ID: <176938201436.4007016.15562827652330249798.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1769012464.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 17:43:34 +0100 you wrote:
> Andy Roulin and Francesco Ruggeri have apparently independently both hit an
> issue with the current neighbor notification scheme. Francesco reported the
> issue in [1]. In a response[2] to that report, Andy said:
>
> neigh_update sends a rtnl notification if an update, e.g.,
> nud_state change, was done but there is no guarantee of
> ordering of the rtnl notifications. Consider the following
> scenario:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] net: core: neighbour: Add a neigh_fill_info() helper for when lock not held
https://git.kernel.org/netdev/net-next/c/77fa50dcb987
- [net-next,v2,2/8] net: core: neighbour: Call __neigh_notify() under a lock
https://git.kernel.org/netdev/net-next/c/0ecdccb8a455
- [net-next,v2,3/8] net: core: neighbour: Extract ARP queue processing to a helper function
https://git.kernel.org/netdev/net-next/c/705ef89ac986
- [net-next,v2,4/8] net: core: neighbour: Process ARP queue later
https://git.kernel.org/netdev/net-next/c/89246ef82d79
- [net-next,v2,5/8] net: core: neighbour: Inline neigh_update_notify() calls
https://git.kernel.org/netdev/net-next/c/a228a7e681b8
- [net-next,v2,6/8] net: core: neighbour: Reorder netlink & internal notification
https://git.kernel.org/netdev/net-next/c/795258891c94
- [net-next,v2,7/8] net: core: neighbour: Make one netlink notification atomically
https://git.kernel.org/netdev/net-next/c/d0887dc8b2d0
- [net-next,v2,8/8] net: core: neighbour: Make another netlink notification atomically
https://git.kernel.org/netdev/net-next/c/a00266969c8e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-25 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 16:43 [PATCH net-next v2 0/8] net: neighbour: Notify changes atomically Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 1/8] net: core: neighbour: Add a neigh_fill_info() helper for when lock not held Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 2/8] net: core: neighbour: Call __neigh_notify() under a lock Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 3/8] net: core: neighbour: Extract ARP queue processing to a helper function Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 4/8] net: core: neighbour: Process ARP queue later Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 5/8] net: core: neighbour: Inline neigh_update_notify() calls Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 6/8] net: core: neighbour: Reorder netlink & internal notification Petr Machata
2026-01-25 22:59 ` Jakub Kicinski
2026-01-21 16:43 ` [PATCH net-next v2 7/8] net: core: neighbour: Make one netlink notification atomically Petr Machata
2026-01-21 16:43 ` [PATCH net-next v2 8/8] net: core: neighbour: Make another " Petr Machata
2026-01-23 15:28 ` [PATCH net-next v2 0/8] net: neighbour: Notify changes atomically Simon Horman
2026-01-25 23:00 ` 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=176938201436.4007016.15562827652330249798.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aroulin@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=leitao@debian.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox