Baker Zhang b5fb82c48b xfrm: use xfrm direction when lookup policy ...

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>
Signed-off-by: David S. Miller <davem@davemloft.net>

2013-03-19 10:35:11 -04:00

..

Kconfig

net/xfrm: remove depends on CONFIG_EXPERIMENTAL

2013-01-11 11:40:03 -08:00

Makefile

…

xfrm_algo.c

pf_key/xfrm_algo: prepare pf_key and xfrm_algo for new algorithms without pfkey support

2013-02-01 10:13:43 +01:00

xfrm_hash.c

…

xfrm_hash.h

…

xfrm_input.c

…

xfrm_ipcomp.c

…

xfrm_output.c

xfrm: fix a unbalanced lock

2013-02-01 10:33:40 +01:00

xfrm_policy.c

xfrm: use xfrm direction when lookup policy

2013-03-19 10:35:11 -04:00

xfrm_proc.c

net: proc: change proc_net_remove to remove_proc_entry

2013-02-18 14:53:08 -05:00

xfrm_replay.c

net/xfrm/xfrm_replay: avoid division by zero

2013-01-18 06:19:49 +01:00

xfrm_state.c

hlist: drop the node parameter from iterators

2013-02-27 19:10:24 -08:00

xfrm_sysctl.c

…

xfrm_user.c

xfrm: Convert xfrm_addr_cmp() to boolean xfrm_addr_equal().

2013-01-29 22:58:40 -05:00