public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: folkert@vanheusden.com (Folkert van Heusden)
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: James Morris <jmorris@redhat.com>,
	lkml Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	sds@epoch.ncsc.mil, Alexander Nyberg <alexn@dsv.su.se>
Subject: Re: [PATCH] SELinux: null dereference in error path
Date: Tue, 1 Mar 2005 17:26:07 +0100	[thread overview]
Message-ID: <20050301162605.GI3318@vanheusden.com> (raw)
In-Reply-To: <F00DE41E-8A09-11D9-858B-000393ACC76E@mac.com>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

> >>The 'bad' label will call function that unconditionally dereferences
> >>the NULL pointer.
> >>Found by the Coverity tool
> >>Signed-off-by: Alexander Nyberg <alexn@dsv.su.se>
> >Signed-off-by: James Morris <jmorris@redhat.com>
> Err, isn't it "Acked-by:"??  I thought "Signed-off-by:" was only for 
> when
> the patch actually went through someone's tree and was forwarded by them
> to somebody else:

Isn't also a good idea to sign your message with gpg or so? That way one
is 100% sure that it *is* that person who is signing-off or acking-by.


Folkert van Heusden

Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See    |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE
Get your PGP/GPG key signed at www.biglumber.com!

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-01 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01  0:32 [PATCH] SELinux: null dereference in error path Alexander Nyberg
2005-03-01  4:11 ` James Morris
2005-03-01  4:25   ` Kyle Moffett
2005-03-01  4:31     ` Andrew Morton
2005-03-01 16:26     ` Folkert van Heusden [this message]
2005-03-01 15:05 ` Stephen Smalley

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=20050301162605.GI3318@vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=sds@epoch.ncsc.mil \
    /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