Re: (usagi-core 30280) Re: [PATCH 10/23] [PATCH] [XFRM]: Trace which secpath state is reject factor.

2006-08-01 Thread Masahide NAKAMURA
David Miller wrote: > From: Masahide NAKAMURA <[EMAIL PROTECTED]> > Date: Sat, 29 Jul 2006 18:30:29 +0900 > >> @@ -272,6 +272,9 @@ #define XFRM_TYPE_NON_FRAGMENT 1 >> void(*destructor)(struct xfrm_state *); >> int (*input)(struct xfrm_state *, st

Re: [PATCH 10/23] [PATCH] [XFRM]: Trace which secpath state is reject factor.

2006-08-01 Thread David Miller
From: Masahide NAKAMURA <[EMAIL PROTECTED]> Date: Sat, 29 Jul 2006 18:30:29 +0900 > @@ -272,6 +272,9 @@ #define XFRM_TYPE_NON_FRAGMENT1 > void(*destructor)(struct xfrm_state *); > int (*input)(struct xfrm_state *, struct sk_buff > *skb); >

[PATCH 10/23] [PATCH] [XFRM]: Trace which secpath state is reject factor.

2006-07-29 Thread Masahide NAKAMURA
For Mobile IPv6 usage, it is required to trace which secpath state is reject factor in order to notify it to user space (to know the address which cannot be used route optimized communication). Based on MIPL2 kernel patch. --- include/net/xfrm.h |3 ++ net/xfrm/xfrm_policy.c | 67 +++