Fan Du e3c0d04750 Fix unexpected SA hard expiration after changing date ... After SA is setup, one timer is armed to detect soft/hard expiration, however the timer handler uses xtime to do the math. This makes hard expiration occurs first before soft expiration after setting new date with big interval. As a result new child SA is deleted before rekeying the new one. Signed-off-by: Fan Du <fdu@windriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2012-08-02 00:19:17 -07:00
..
Kconfig
Makefile
xfrm_algo.c
xfrm_hash.c
xfrm_hash.h
xfrm_input.c
xfrm_ipcomp.c
xfrm_output.c
xfrm_policy.c	net: Document dst->obsolete better.	2012-07-20 13:31:21 -07:00
xfrm_proc.c
xfrm_replay.c
xfrm_state.c	Fix unexpected SA hard expiration after changing date	2012-08-02 00:19:17 -07:00
xfrm_sysctl.c
xfrm_user.c	netlink: add netlink_kernel_cfg parameter to netlink_kernel_create	2012-06-29 16:46:02 -07:00