From: Steffen Klassert <steffen.klassert@secunet.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
David Miller <davem@davemloft.net>
Cc: David Ahern <dsa@cumulusnetworks.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec-next v2] xfrm: Use VRF master index if output device is enslaved
Date: Fri, 21 Aug 2015 22:31:32 +0200 [thread overview]
Message-ID: <20150821203132.GA3589@secunet.com> (raw)
In-Reply-To: <E97BEDFF-A3B2-41B4-A669-969E7052C75E@cumulusnetworks.com>
On Fri, Aug 21, 2015 at 02:11:21AM +0300, Nikolay Aleksandrov wrote:
>
> > On Aug 21, 2015, at 1:06 AM, David Ahern <dsa@cumulusnetworks.com> wrote:
> >
> > Directs route lookups to VRF table. Compiles out if NET_VRF is not
> > enabled. With this patch able to successfully bring up ipsec tunnels
> > in VRFs, even with duplicate network configuration.
> >
> > Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
> > ---
> > v2
> > - use vrf_master_ifindex rather than vrf_master_ifindex_rcu
> >
> > net/ipv4/xfrm4_policy.c | 7 +++++--
> > net/ipv6/xfrm6_policy.c | 7 +++++--
> > 2 files changed, 10 insertions(+), 4 deletions(-)
> >
>
> Looks good to me,
>
> Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
David, can you please take this directly into net-next?
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
next prev parent reply other threads:[~2015-08-21 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 22:06 [PATCH ipsec-next v2] xfrm: Use VRF master index if output device is enslaved David Ahern
2015-08-20 23:11 ` Nikolay Aleksandrov
2015-08-21 20:31 ` Steffen Klassert [this message]
2015-08-25 18:25 ` 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=20150821203132.GA3589@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.