From: Paolo Abeni <pabeni@redhat.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Beniamino Galvani <bgalvani@redhat.com>
Subject: Re: [PATCH net v2] ipv6: enforce egress device match in per table nexthop lookups
Date: Thu, 23 Jun 2016 16:39:22 +0200 [thread overview]
Message-ID: <1466692762.4910.48.camel@redhat.com> (raw)
In-Reply-To: <14311cf1-0b8e-cde2-54c0-c49a1b39b0c6@cumulusnetworks.com>
On Thu, 2016-06-23 at 08:29 -0600, David Ahern wrote:
> On 6/23/16 8:20 AM, David Ahern wrote:
> >> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> >> index 969913d..520b788 100644
> >> --- a/net/ipv6/route.c
> >> +++ b/net/ipv6/route.c
> >> @@ -1782,7 +1782,7 @@ static struct rt6_info
> >> *ip6_nh_lookup_table(struct net *net,
> >> };
> >> struct fib6_table *table;
> >> struct rt6_info *rt;
> >> - int flags = 0;
> >> + int flags = RT6_LOOKUP_F_IFACE;
> >>
> >> table = fib6_get_table(net, cfg->fc_table);
> >> if (!table)
> >>
> >
> > Acked-by: David Ahern <dsa@cumulusnetworks.com>
>
> I take that back.
>
> I think RT6_LOOKUP_F_IFACE should only be set if cfg->fc_ifindex is set.
AFAICS the latter condition should not be needed. The related
information is passed all way down to rt6_score_route(), where it's
really used:
m = rt6_check_dev(rt, oif);
if (!m && (strict & RT6_LOOKUP_F_IFACE))
return RT6_NUD_FAIL_HARD;
and 'm' can be 0 only if oif is set: RT6_LOOKUP_F_IFACE has no effect
ifindex is set.
Paolo
next prev parent reply other threads:[~2016-06-23 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 13:25 [PATCH net v2] ipv6: enforce egress device match in per table nexthop lookups Paolo Abeni
2016-06-23 14:20 ` David Ahern
2016-06-23 14:29 ` David Ahern
2016-06-23 14:39 ` Paolo Abeni [this message]
2016-06-23 20:33 ` David Ahern
2016-06-27 14:37 ` 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=1466692762.4910.48.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=bgalvani@redhat.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.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 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).