From: David Ahern <dsahern@gmail.com>
To: Donald Sharp <sharpd@cumulusnetworks.com>,
netdev@vger.kernel.org, Thomas.Winter@alliedtelesis.co.nz,
nikolay@cumulusnetworks.com, yotamg@mellanox.com,
idosch@mellanox.com, roopa@cumulusnetworks.com
Subject: Re: [PATCH net v3] net: ipmr: Fix some mroute forwarding issues in vrf's
Date: Sat, 10 Jun 2017 17:32:33 -0600 [thread overview]
Message-ID: <25a39bcd-d623-951a-75c5-773b2cc0518e@gmail.com> (raw)
In-Reply-To: <20170610203017.4085-1-sharpd@cumulusnetworks.com>
On 6/10/17 2:30 PM, Donald Sharp wrote:
> 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@cumulusnetworks.com>
> ---
> v2: Fixed title
> v3: Addressed Review comments by Andrew Lunn and David Ahern
>
LGTM.
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2017-06-10 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 20:30 [PATCH net v3] net: ipmr: Fix some mroute forwarding issues in vrf's Donald Sharp
2017-06-10 23:07 ` David Miller
2017-06-10 23:33 ` David Ahern
2017-06-10 23:39 ` Thomas Winter
2017-06-10 23:32 ` David Ahern [this message]
2017-06-11 0:21 ` Nikolay Aleksandrov
2017-06-11 6:12 ` Yotam Gigi
2017-06-11 22:15 ` David Miller
2017-06-12 2:55 ` David Ahern
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=25a39bcd-d623-951a-75c5-773b2cc0518e@gmail.com \
--to=dsahern@gmail.com \
--cc=Thomas.Winter@alliedtelesis.co.nz \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=sharpd@cumulusnetworks.com \
--cc=yotamg@mellanox.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).