Re: [PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved

2015-08-19 Thread Steffen Klassert
On Wed, Aug 19, 2015 at 11:35:55AM -0700, David Ahern wrote: > > > >I think you should use the new vrf_master_index() helper that acquires rcu > >because > >it looks possible to call ->decode_session() without rcu read lock, e.g. in > >the hold_timer > >function xfrm_policy_queue_process(), thoug

Re: [PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved

2015-08-19 Thread David Ahern
On 8/19/15 5:47 AM, Nikolay Aleksandrov wrote: On Aug 18, 2015, at 6:54 PM, David Ahern 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 (IPv4 teste

Re: [PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved

2015-08-19 Thread Nikolay Aleksandrov
> On Aug 18, 2015, at 6:54 PM, David Ahern 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 (IPv4 tested). > > Signed-off-by: David Ahern > -

[PATCH ipsec-next] xfrm: Use VRF master index if output device is enslaved

2015-08-18 Thread David Ahern
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 (IPv4 tested). Signed-off-by: David Ahern --- net/ipv4/xfrm4_policy.c | 7 +-- net/ipv6/xfrm6_policy.c |