From: Jakub Kicinski <kuba@kernel.org>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] ip6mr: implement RTM_GETROUTE for single entry
Date: Thu, 30 Jun 2022 20:27:06 -0700 [thread overview]
Message-ID: <20220630202706.33555ad2@kernel.org> (raw)
In-Reply-To: <20220630133051.41685-1-equinox@diac24.net>
On Thu, 30 Jun 2022 15:30:49 +0200 David Lamparter wrote:
> The IPv6 multicast routing code implements RTM_GETROUTE, but only for a
> dump request. Retrieving a single MFC entry is not currently possible
> via netlink.
>
> While most of the data here can also be retrieved with SIOCGETSGCNT_IN6,
> the lastused / RTA_EXPIRES is not included in the ioctl result (and we
> need it in FRR.)
>
> => Implement single-entry RTM_GETROUTE by copying and adapting the IPv4
> code.
>
> Tested against FRRouting's (work-in-progress) IPv6 PIM implementation.
You must CC maintainers (./scripts/get_maintainer.pl). With the patch
volume on netdev and constant trouble with gmail the chances of people
missing a submission are just too high. Please repost.
next prev parent reply other threads:[~2022-07-01 3:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 13:30 [PATCH net-next 0/2] ip6mr: implement RTM_GETROUTE for single entry David Lamparter
2022-06-30 13:30 ` [PATCH 1/2] ipv6: make rtm_ipv6_policy available David Lamparter
2022-06-30 13:30 ` [PATCH 2/2] net: ip6mr: add RTM_GETROUTE netlink op David Lamparter
2022-07-01 3:27 ` Jakub Kicinski [this message]
2022-07-01 7:58 ` [PATCH resend net-next 0/2] ip6mr: implement RTM_GETROUTE for single entry David Lamparter
2022-07-01 7:58 ` [PATCH net-next 1/2] ipv6: make rtm_ipv6_policy available David Lamparter
2022-07-01 7:58 ` [PATCH net-next 2/2] net: ip6mr: add RTM_GETROUTE netlink op David Lamparter
2022-07-03 19:07 ` David Ahern
2022-07-04 8:35 ` David Lamparter
2022-07-04 9:58 ` [PATCH net-next v2] " David Lamparter
2022-07-04 10:22 ` Nikolay Aleksandrov
2022-07-04 10:38 ` David Lamparter
2022-07-04 10:44 ` Nikolay Aleksandrov
2022-07-04 10:52 ` [PATCH net-next v3] " David Lamparter
2022-07-05 2:50 ` Jakub Kicinski
2022-07-06 9:52 ` David Lamparter
2022-07-05 3:38 ` [PATCH net-next v2] " kernel test robot
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=20220630202706.33555ad2@kernel.org \
--to=kuba@kernel.org \
--cc=equinox@diac24.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).