[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170611.181556.1883936192698112580.davem@davemloft.net>
Date: Sun, 11 Jun 2017 18:15:56 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: sharpd@...ulusnetworks.com
Cc: netdev@...r.kernel.org, dsahern@...il.com,
Thomas.Winter@...iedtelesis.co.nz, nikolay@...ulusnetworks.com,
yotamg@...lanox.com, idosch@...lanox.com, roopa@...ulusnetworks.com
Subject: Re: [PATCH net v3] net: ipmr: Fix some mroute forwarding issues in
vrf's
From: Donald Sharp <sharpd@...ulusnetworks.com>
Date: Sat, 10 Jun 2017 16:30:17 -0400
> This patch fixes two issues:
>
> 1) When forwarding on *,G mroutes that are in a vrf, the
> kernel was dropping information about the actual incoming
> interface when calling ip_mr_forward from ip_mr_input.
> This caused ip_mr_forward to send the multicast packet
> back out the incoming interface. Fix this by
> modifying ip_mr_forward to be handed the correctly
> resolved dev.
>
> 2) When a unresolved cache entry is created we store
> the incoming skb on the unresolved cache entry and
> upon mroute resolution from the user space daemon,
> we attempt to forward the packet. Again we were
> not resolving to the correct incoming device for
> a vrf scenario, before calling ip_mr_forward.
> Fix this by resolving to the correct interface
> and calling ip_mr_forward with the result.
>
> Fixes: e58e41596811 ("net: Enable support for VRF with ipv4 multicast")
> Signed-off-by: Donald Sharp <sharpd@...ulusnetworks.com>
> ---
> v2: Fixed title
> v3: Addressed Review comments by Andrew Lunn and David Ahern
Applied and queued up for -stable, thank you.
Powered by blists - more mailing lists