public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: dhowells@redhat.com, safford@watson.ibm.com, safford@us.ibm.com,
	jj@chaosbits.net, jmorris@namei.org, keyrings@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] trusted-keys: check for NULL before using it
Date: Mon, 17 Jan 2011 09:34:55 +0000	[thread overview]
Message-ID: <3575.1295256895@redhat.com> (raw)
In-Reply-To: <201101170041.p0H0ffFE086481@www262.sakura.ne.jp>

Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:

> From 8118c3d0d6f2b291d56e2f4475f2aa5156299cf3 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Mon, 17 Jan 2011 09:25:34 +0900
> Subject: [PATCH 2/3] trusted-keys: check for NULL before using it
> 
> TSS_rawhmac() checks for data != NULL before using it.
> We should do the same thing for TSS_authhmac().
> 
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>

Acked-by: David Howells <dhowells@redhat.com>

  parent reply	other threads:[~2011-01-17  9:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 20:07 [PATCH] Trusted and Encrypted Keys: fix up TSS_rawhmac() so we always kfree() and remember to call va_end() Jesper Juhl
2011-01-14 13:28 ` David Safford
2011-01-14 13:45   ` [PATCH] Trusted and Encrypted Keys: fix up TSS_rawhmac() so wealways " Tetsuo Handa
2011-01-14 14:07     ` Tetsuo Handa
2011-01-15  0:58       ` Tetsuo Handa
2011-01-16 14:04       ` Jesper Juhl
2011-01-17  0:39         ` [PATCH 1/3] trusted-keys: another free memory bugfix Tetsuo Handa
2011-01-17  0:41           ` [PATCH 2/3] trusted-keys: check for NULL before using it Tetsuo Handa
2011-01-17  0:44             ` [PATCH 3/3] trusted-keys: avoid scattring va_end() Tetsuo Handa
2011-01-17  9:39               ` David Howells
2011-01-17 18:36               ` Jesper Juhl
2011-01-17 21:06               ` Mimi Zohar
2011-01-18  1:39                 ` [PATCH 3/3] trusted-keys: small cleanup Tetsuo Handa
2011-01-18  9:26                   ` Mimi Zohar
2011-01-18 11:03                     ` Tetsuo Handa
2011-01-18 11:28                       ` Mimi Zohar
2011-01-18 11:42                         ` Mimi Zohar
2011-01-17  9:34             ` David Howells [this message]
2011-01-17 18:35             ` [PATCH 2/3] trusted-keys: check for NULL before using it Jesper Juhl
2011-01-17 21:02             ` Mimi Zohar
2011-01-17  9:33           ` [PATCH 1/3] trusted-keys: another free memory bugfix David Howells
2011-01-17 18:34           ` Jesper Juhl
2011-01-17 21:01           ` Mimi Zohar
2011-01-18 22:55           ` James Morris
2011-01-14 13:31 ` [PATCH] Trusted and Encrypted Keys: fix up TSS_rawhmac() so we always kfree() and remember to call va_end() David Howells

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=3575.1295256895@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jj@chaosbits.net \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=safford@us.ibm.com \
    --cc=safford@watson.ibm.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