netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: patch: policy update by id
Date: Wed, 27 Apr 2005 21:13:36 -0400	[thread overview]
Message-ID: <1114650816.7663.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20050427233924.GA22238@gondor.apana.org.au>

On Thu, 2005-28-04 at 09:39 +1000, Herbert Xu wrote:
> On Wed, Apr 27, 2005 at 08:27:06AM -0400, Jamal Hadi Salim wrote:
> >
> > --- /usr/src/26117-mod/net/xfrm/xfrm_policy.c	2005/04/27 11:32:13	1.1
> > +++ /usr/src/26117-mod/net/xfrm/xfrm_policy.c	2005/04/27 12:25:24
> > @@ -345,7 +345,9 @@
> >  
> >  	write_lock_bh(&xfrm_policy_lock);
> >  	for (p = &xfrm_policy_list[dir]; (pol=*p)!=NULL;) {
> > -		if (!delpol && memcmp(&policy->selector, &pol->selector, sizeof(pol->selector)) == 0) {
> > +		if (!delpol && 
> > +		((!excl && policy->index && (policy->index == pol->index)) || 
> > +		 (memcmp(&policy->selector, &pol->selector, sizeof(pol->selector)) == 0))) {
> 
> I have no problems with the idea itself.  However, I have a couple of
> minor issues with this patch :)
> 
> First of all please align the continued lines to the if expression, e.g.,
> 		if (!delpol && 
> 		    (policy->index && (policy->index == pol->index)) || 
> 

np. sorry, i was rushing out - testing as we speak.

> Also the excl check doesn't make sense.  You should let the
> following excl check take place after you've found out that
> the indices is identical.
> 

the policy->index is only relevant for the update not the add;
the update could also be done by selector. So i didnt follow.

cheers,
jamal 

  reply	other threads:[~2005-04-28  1:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 11:54 patch: policy update by id Jamal Hadi Salim
2005-04-27 12:18 ` Patrick McHardy
2005-04-27 12:28   ` Jamal Hadi Salim
2005-04-27 12:52     ` jamal
2005-04-27 12:24 ` jamal
2005-04-27 12:27   ` Jamal Hadi Salim
2005-04-27 23:39     ` Herbert Xu
2005-04-28  1:13       ` jamal [this message]
2005-04-28  1:21         ` Herbert Xu
2005-04-28  1:30           ` Herbert Xu
2005-04-28  1:52             ` jamal
2005-04-28  2:07               ` Herbert Xu
2005-04-28  2:20                 ` jamal
2005-04-28  2:22                   ` Herbert Xu
2005-04-28  2:29                     ` jamal
2005-04-28  2:43                 ` David S. Miller
2005-04-28  2:56                   ` Herbert Xu
2005-04-28  3:16                     ` jamal
2005-04-28  3:20                       ` Herbert Xu
2005-04-28 11:43                         ` Thomas Graf
2005-04-28 12:09                           ` Patrick McHardy
2005-04-28 12:33                             ` Thomas Graf
2005-04-28  3:09                   ` jamal
2005-04-28  1:44           ` jamal
2005-04-28  1:48             ` Herbert Xu
2005-04-28  1:59               ` jamal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1114650816.7663.13.camel@localhost.localdomain \
    --to=hadi@cyberus.ca \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).