From: David Ahern <dsahern@gmail.com>
To: Sabrina Dubroca <sd@queasysnail.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: don't return invalid table id error when we fall back to PF_UNSPEC
Date: Wed, 20 May 2020 07:40:13 -0600 [thread overview]
Message-ID: <1b129a24-57a8-4240-07c2-bfaa6231bf92@gmail.com> (raw)
In-Reply-To: <fc61912d585ccf3999c3cba5e481c1920af17ca6.1589961603.git.sd@queasysnail.net>
On 5/20/20 3:15 AM, Sabrina Dubroca wrote:
> In case we can't find a ->dumpit callback for the requested
> (family,type) pair, we fall back to (PF_UNSPEC,type). In effect, we're
> in the same situation as if userspace had requested a PF_UNSPEC
> dump. For RTM_GETROUTE, that handler is rtnl_dump_all, which calls all
> the registered RTM_GETROUTE handlers.
...
> Instead, this patch removes dump_all_families and updates the
> RTM_GETROUTE handlers to check if the family that is being dumped is
> their own. When it's not, which covers both the intentional PF_UNSPEC
> dumps (as dump_all_families did) and the fallback case, ignore the
> missing table id error.
>
> Fixes: cb167893f41e ("net: Plumb support for filtering ipv4 and ipv6 multicast route dumps")
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
> ---
> include/net/ip_fib.h | 1 -
> net/ipv4/fib_frontend.c | 3 +--
> net/ipv4/ipmr.c | 2 +-
> net/ipv6/ip6_fib.c | 2 +-
> net/ipv6/ip6mr.c | 2 +-
> 5 files changed, 4 insertions(+), 6 deletions(-)
>
Thanks for the detailed analysis and commit message.
Reviewed-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2020-05-20 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 9:15 [PATCH net] net: don't return invalid table id error when we fall back to PF_UNSPEC Sabrina Dubroca
2020-05-20 13:40 ` David Ahern [this message]
2020-05-22 0:26 ` David Miller
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=1b129a24-57a8-4240-07c2-bfaa6231bf92@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).