netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Venkat Yekkirala" <vyekkirala@trustedcs.com>
To: "'James Morris'" <jmorris@namei.org>
Cc: "'Eric Paris'" <eparis@parisplace.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Venkat Yekkirala" <vyekkirala@tcsfw4.tcs-sec.com>,
	<cxzhang@watson.ibm.com>, "Stephen Smalley" <sds@tycho.nsa.gov>
Subject: RE: [PATCH] xfrm_policy delete security check misplaced
Date: Mon, 5 Mar 2007 11:10:04 -0600	[thread overview]
Message-ID: <001801c75f49$1e1989f0$cc0a010a@tcssec.com> (raw)
In-Reply-To: <Line.LNX.4.64.0703051139040.14821@d.namei>

> > > 
> > > Signed-off-by: Eric Paris <eparis@redhat.com>
> > Acked-by: Venkat Yekkirala <vyekkirala@trustedcs.com> 
> 
> What about your previous comment:
> 
>  "I guess you meant to do this here?
>         else if (err)
>                 return err; "

I saw that this was taken care of in patch-2 for the delete case, but
while err isn't currently applicable to the non-delete case, it would
be proper/complete for err to still be handled for the non-delete case.
Thanks for asking.

  parent reply	other threads:[~2007-03-05 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 18:29 [PATCH] xfrm_policy delete security check misplaced Eric Paris
2007-03-05 15:33 ` Venkat Yekkirala
2007-03-05 15:58 ` Venkat Yekkirala
2007-03-05 16:39   ` James Morris
2007-03-05 16:51     ` Eric Paris
2007-03-05 17:10     ` Venkat Yekkirala [this message]
2007-03-06  0:37 ` James Morris
2007-03-07 23:38 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-03-05 15:36 Venkat Yekkirala

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='001801c75f49$1e1989f0$cc0a010a@tcssec.com' \
    --to=vyekkirala@trustedcs.com \
    --cc=cxzhang@watson.ibm.com \
    --cc=davem@davemloft.net \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=vyekkirala@tcsfw4.tcs-sec.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).