From: Sabrina Dubroca <sd@queasysnail.net>
To: netdev@vger.kernel.org
Cc: Sabrina Dubroca <sd@queasysnail.net>,
Kuniyuki Iwashima <kuniyu@google.com>,
David Ahern <dsahern@kernel.org>
Subject: [PATCH net 0/2] neighbour: fix update of proxy neighbour
Date: Tue, 10 Mar 2026 22:59:15 +0100 [thread overview]
Message-ID: <cover.1772894876.git.sd@queasysnail.net> (raw)
While re-reading some "old" patches I ran into a small change of
behavior in commit dc2a27e524ac ("neighbour: Update pneigh_entry in
pneigh_create().").
The old behavior was not consistent between ->protocol and ->flags,
and didn't offer a way to clear protocol, so maybe it's better to
change that (7-years-old [1]) behavior. But then we should change
non-proxy neighbours as well to keep neigh/pneigh consistent.
[1] df9b0e30d44c ("neighbor: Add protocol attribute")
Sabrina Dubroca (2):
neighbour: restore protocol != 0 check in pneigh update
selftests: rtnetlink: add neighbour update test
net/core/neighbour.c | 3 +-
tools/testing/selftests/net/rtnetlink.sh | 55 ++++++++++++++++++++++++
2 files changed, 57 insertions(+), 1 deletion(-)
--
2.51.2
next reply other threads:[~2026-03-10 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 21:59 Sabrina Dubroca [this message]
2026-03-10 21:59 ` [PATCH net 1/2] neighbour: restore protocol != 0 check in pneigh update Sabrina Dubroca
2026-03-10 23:16 ` David Ahern
2026-03-11 4:04 ` Kuniyuki Iwashima
2026-03-10 21:59 ` [PATCH net 2/2] selftests: rtnetlink: add neighbour update test Sabrina Dubroca
2026-03-11 4:10 ` Kuniyuki Iwashima
2026-03-12 2:10 ` [PATCH net 0/2] neighbour: fix update of proxy neighbour patchwork-bot+netdevbpf
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=cover.1772894876.git.sd@queasysnail.net \
--to=sd@queasysnail.net \
--cc=dsahern@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.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.