You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

David S. Miller d49c73c729 [IPSEC]: Validate properly in xfrm_dst_check() ... If dst->obsolete is -1, this is a signal from the bundle creator that we want the XFRM dst and the dsts that it references to be validated on every use. I misunderstood this intention when I changed xfrm_dst_check() to always return NULL. Now, when we purge a dst entry, by running dst_free() on it. This will set the dst->obsolete to a positive integer, and we want to return NULL in that case so that the socket does a relookup for the route. Thus, if dst->obsolete<0, let stale_bundle() validate the state, else always return NULL. In general, we need to do things more intelligently here because we flush too much state during rule changes. Herbert Xu has some ideas wherein the key manager gives us some help in this area. We can also use smarter state management algorithms inside of the kernel as well. Signed-off-by: David S. Miller <davem@davemloft.net>		19 years ago
..
Kconfig	…
Makefile	…
xfrm_algo.c	Remove obsolete #include <linux/config.h>	19 years ago
xfrm_input.c	…
xfrm_policy.c	[IPSEC]: Validate properly in xfrm_dst_check()	19 years ago
xfrm_state.c	[NET]: Conversions from kmalloc+memset to k(z|c)alloc.	19 years ago
xfrm_user.c	[NETLINK]: Encapsulate eff_cap usage within security framework.	19 years ago