From: Paolo Abeni <pabeni@redhat.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Hajime Tazaki <thehajime@gmail.com>,
lucien.xin@gmail.com,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Subject: Re: [PATCH net 1/2] ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
Date: Thu, 28 Jan 2016 18:04:53 +0100 [thread overview]
Message-ID: <1454000693.27229.15.camel@redhat.com> (raw)
In-Reply-To: <56AA2CE5.2050307@cumulusnetworks.com>
On Thu, 2016-01-28 at 07:59 -0700, David Ahern wrote:
> On 1/27/16 6:45 AM, Paolo Abeni wrote:
> > The current implementation of ip6_dst_lookup_tail() basically
> > ignore the egress ifindex match: if the saddr is set,
> > ip6_route_output() purposefully ignores flowi6_oif, due
> > to the commit d46a9d678e4c ("net: ipv6: Dont add RT6_LOOKUP_F_IFACE
> > flag if saddr set"), if the saddr is 'any' the first route lookup
> > in ip6_dst_lookup_tail fails, but upon failure a second lookup will
> > be performed with saddr set, thus ignoring the ifindex constraint.
> >
> > This commit adds an output route lookup function variant, which
> > allows the caller to specify additional lookup flags, and modify
> > ip6_dst_lookup_tail() to enforce the ifindex match on the second
> > lookup via said helper.
> >
> > Fixes: d46a9d678e4c ("net: ipv6: Dont add RT6_LOOKUP_F_IFACE flag if saddr set")
> > Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>
> I don't agree with that 'Fixes:' tag.
>
> ip6_route_output did not add the RT6_LOOKUP_F_IFACE flag until
> 741a11d9e410; d46a9d678e4c is a follow on to limit adding the flag only
> if no source address is given.
>
> Since ip6_dst_lookup_tail never considered the flowi6_oif this is a
> general bug fix rather than a fix of d46a9d678e4c.
Ok, I'll remove it in the v2, which will include Hannes feedback, too.
Regards,
Paolo
next prev parent reply other threads:[~2016-01-28 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:45 [PATCH net 0/2] ipv6: fix sticky pktinfo behaviour Paolo Abeni
2016-01-27 13:45 ` [PATCH net 1/2] ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail() Paolo Abeni
2016-01-27 18:38 ` Hannes Frederic Sowa
2016-01-28 12:27 ` Paolo Abeni
2016-01-28 13:02 ` Hannes Frederic Sowa
2016-01-28 14:59 ` David Ahern
2016-01-28 17:04 ` Paolo Abeni [this message]
2016-01-27 13:45 ` [PATCH net 2/2] ipv6/udp: use sticky pktinfo egress ifindex on connect() Paolo Abeni
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=1454000693.27229.15.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=thehajime@gmail.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 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).