Re: [PATCH] use xfrm direction when lookup policy

From: David Miller
Date: Tue Mar 19 2013 - 10:35:43 EST

From: Baker Zhang <baker.kernel@xxxxxxxxx>
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@xxxxxxxxx>

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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at