[Top] [All Lists]

Re: patch: policy update by id

To: jamal <hadi@xxxxxxxxxx>
Subject: Re: patch: policy update by id
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Apr 2005 11:48:18 +1000
Cc: netdev@xxxxxxxxxxx
In-reply-to: <1114652680.7663.31.camel@xxxxxxxxxxxxxxxxxxxxx>
References: <1114602874.7670.4.camel@xxxxxxxxxxxxxxxxxxxxx> <1114604657.7670.22.camel@xxxxxxxxxxxxxxxxxxxxx> <1114604826.7670.24.camel@xxxxxxxxxxxxxxxxxxxxx> <20050427233924.GA22238@xxxxxxxxxxxxxxxxxxx> <1114650816.7663.13.camel@xxxxxxxxxxxxxxxxxxxxx> <20050428012135.GA22950@xxxxxxxxxxxxxxxxxxx> <1114652680.7663.31.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
On Wed, Apr 27, 2005 at 09:44:40PM -0400, jamal wrote:
> > I see.  In that case you want to change your expression above
> > so that the memcmp is never done if excl is off and the index
> > is non-zero.
> Hrm. Thinking... So you want to exclude the selector check if someone
> updating ever specified the index? That may change things a little, no?
> Give me a clever expression.

Please see my last email.  To do index updates correctly we'll need
to modify the current code so that it is able to delete two existing
policies.  We may have two existing policies if one matches the index
while the other matches the selector.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:

<Prev in Thread] Current Thread [Next in Thread>