From: Baker Zhang <[email protected]> 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 <[email protected]> Since this is a cleanup and doesn't really fix a bug, I've applied this to net-next. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
