Messages in this thread | | | Date | Tue, 19 Mar 2013 10:35:36 -0400 (EDT) | Subject | Re: [PATCH] use xfrm direction when lookup policy | From | David Miller <> |
| |
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.
| |