[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.11.1404280949410.1587@ja.home.ssi.bg>
Date: Mon, 28 Apr 2014 10:07:27 +0300 (EEST)
From: Julian Anastasov <ja@....bg>
To: Lorenzo Colitti <lorenzo@...gle.com>
cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
David Miller <davem@...emloft.net>, JP Abgrall <jpa@...gle.com>
Subject: Re: [RFC net-next 1/4] net: ipv6: Introduce flowi6_init_output.
Hello,
On Sun, 27 Apr 2014, Lorenzo Colitti wrote:
> On Sat, Apr 26, 2014 at 2:56 PM, Julian Anastasov <ja@....bg> wrote:
> >> + fl6->flowi6_oif = oif;
> >> + fl6->flowi6_iif = 0;
> >
> > Make sure LOOPBACK_IFINDEX is provided in
> > flowi6_iif instead of 0, recent commit fixed such
> > FIB rule lookups.
>
> I'm assuming that was for IPv4? All the IPv6 code in current net-next
> still seems to set flowi6_iif to zero. It's later set to
> LOOPBACK_IFINDEX in ip6_route_output.
I see, it seems more IPv6 places need a fix.
> You could argue that if this patch is accepted, then setting
> flowi6_iif to LOOPBACK_IFINDEX belongs there for consistency with
> IPv4. That seems reasonable, but I'd prefer not doing that in this
> patch because 1) this patch is semantically a no-op and I'd like to
> keep it that way, 2) it would be a bigger change, because even with
> this patch, there are still codepaths that initialize their own flowi6
> and memset them to zero.
OK. I'll try a patch to fix the remaining flowi6_iif
places...
Regards
--
Julian Anastasov <ja@....bg>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists