lkml.org 
[lkml]   [2013]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] use xfrm direction when lookup policy
From
From: Baker Zhang <baker.kernel@gmail.com>
Date: Tue, 19 Mar 2013 22:24:30 +0800

> because xfrm policy direction has same value with corresponding
> flow direction, so this problem is covered.
>
> In xfrm_lookup and __xfrm_policy_check, flow_cache_lookup is used to
> accelerate the lookup.
>
> Flow direction is given to flow_cache_lookup by policy_to_flow_dir.
>
> When the flow cache is mismatched, callback 'resolver' is called.
>
> 'resolver' requires xfrm direction,
> so convert direction back to xfrm direction.
>
> Signed-off-by: Baker Zhang <baker.zhang@gmail.com>

Since this is a cleanup and doesn't really fix a bug, I've applied
this to net-next.

Thanks.


\
 
 \ /
  Last update: 2013-03-19 20:42    [W:0.021 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site