From: Stephen Hemminger <stephen@networkplumber.org>
To: Matt Muggeridge <Matt.Muggeridge@hpe.com>
Cc: 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>,
netdev@vger.kernel.org
Subject: Re: [PATCH net 0/1] net/ipv6: Netlink flag for new IPv6 Default Routes
Date: Sat, 9 Nov 2024 14:53:35 -0800 [thread overview]
Message-ID: <20241109145335.0e9f3f62@hermes.local> (raw)
In-Reply-To: <20241105031841.10730-1-Matt.Muggeridge@hpe.com>
On Mon, 4 Nov 2024 22:18:38 -0500
Matt Muggeridge <Matt.Muggeridge@hpe.com> wrote:
> This is the cover letter and provides a brief overview of the change.
>
> Add a Netlink rtm_flag, RTM_F_RA_ROUTER for the RTM_NEWROUTE message.
> This allows an IPv6 Netlink client to indicate the default route came
> from an RA. This results in the kernel creating individual default
> routes, rather than coalescing multiple default routes into a single
> ECMP route.
>
> This change also needs to be reflected in the man7/rtnetlink.7 page. Below is
> the one-line addition to the man-pages git repo
> (https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git):
>
> diff --git a/man/man7/rtnetlink.7 b/man/man7/rtnetlink.7
> index 86ed459bb..07c4ef0a8 100644
> --- a/man/man7/rtnetlink.7
> +++ b/man/man7/rtnetlink.7
> @@ -295,6 +295,7 @@ if the route changes, notify the user via rtnetlink
> T}
> RTM_F_CLONED:route is cloned from another route
> RTM_F_EQUALIZE:a multipath equalizer (not yet implemented)
> +RTM_F_RA_ROUTER: the route is a default route from an RA
> .TE
> .IP
> .I rtm_table
>
>
> Signed-off-by: Matt Muggeridge <Matt.Muggeridge@hpe.com>
> Cc: David Ahern <dsahern@kernel.org>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: linux-api@vger.kernel.org
> Cc: stable@vger.kernel.org
>
> Matt Muggeridge (1):
> net/ipv6: Netlink flag for new IPv6 Default Routes
>
> include/uapi/linux/rtnetlink.h | 9 +++++----
> net/ipv6/route.c | 3 +++
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
>
> base-commit: 5ccdcdf186aec6b9111845fd37e1757e9b413e2f
Please send this to Linux man page maintainers.
It isn't really a linux-api type change.
Not sure if man pages project does a stable tree.
https://www.kernel.org/doc/man-pages/maintaining.html#:~:text=Maintaining%20Linux%20man-pages%20The%20current%20man-pages%20maintainer%20is,2020%2C%20Alejandro%20Colomar%20%28alx.manpages%40gmail.com%29%20has%20joined%20as%20comaintainer.
prev parent reply other threads:[~2024-11-09 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 3:18 [PATCH net 0/1] net/ipv6: Netlink flag for new IPv6 Default Routes Matt Muggeridge
2024-11-05 3:18 ` [PATCH net 1/1] " Matt Muggeridge
2024-11-05 14:37 ` Nicolas Dichtel
2024-11-06 1:44 ` Matt Muggeridge
2024-11-05 18:15 ` Ido Schimmel
2024-11-06 2:50 ` Matt Muggeridge
2024-11-06 12:37 ` Ido Schimmel
2024-11-07 3:53 ` Matt Muggeridge
2024-11-07 9:52 ` Ido Schimmel
2024-11-08 2:20 ` Matt Muggeridge
2024-11-14 20:42 ` Matt Muggeridge
2024-11-06 18:59 ` David Ahern
2024-11-09 22:53 ` Stephen Hemminger [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=20241109145335.0e9f3f62@hermes.local \
--to=stephen@networkplumber.org \
--cc=Matt.Muggeridge@hpe.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.