| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [2/4] [IPSEC] Kill spurious hard expire messages |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 11 Apr 2005 07:20:20 -0400 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, Masahide NAKAMURA <nakam@xxxxxxxxxxxxxx>, Patrick McHardy <kaber@xxxxxxxxx>, netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20050410212707.GA30337@gondor.apana.org.au> |
| Organization: | jamalopolous |
| References: | <1112702604.1089.119.camel@jzny.localdomain> <20050409105452.GA7171@gondor.apana.org.au> <20050409111244.GB7171@gondor.apana.org.au> <1113049844.1090.23.camel@jzny.localdomain> <20050409192926.GA9423@gondor.apana.org.au> <20050409200306.GA9660@gondor.apana.org.au> <1113142244.1088.287.camel@jzny.localdomain> <20050410212707.GA30337@gondor.apana.org.au> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Herbert,
On Sun, 2005-04-10 at 17:27, Herbert Xu wrote:
>
> What I am saying is that this is impossible. If it really bothers you
> we can turn the WARN_ON into a BUG.
>
We started this discussion by asserting that an expire may be issued on
a policy (or state) despite a delete event notification already having
happened. Thats what we were/are trying to stop, no?
What i am saying is you are not stopping that with this:
---
if (!xfrm_policy_delete(xp, dir))
km_policy_expired(xp, dir, 1);
---
xfrm_policy_delete will return 0 whether the policy is dead or not.
OTOH, if it returns <0 for the case where it is dead, then an expire
event will not be issued.
cheers,
jamal
|
| Previous by Date: | Re: [Fwd: Re: connector is missing in 2.6.12-rc2-mm1], Evgeniy Polyakov |
|---|---|
| Next by Date: | Re: [5/*] [IPSEC] Use XFRM_MSG_* instead of XFRM_SAP_*, jamal |
| Previous by Thread: | Re: [2/4] [IPSEC] Kill spurious hard expire messages, Herbert Xu |
| Next by Thread: | Re: [2/4] [IPSEC] Kill spurious hard expire messages, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |