From: Kees Cook <kees.cook@canonical.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Stefan Ringel <stefan.ringel@arcor.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] staging: fix possible use-before-NULL-check crash
Date: Wed, 6 Oct 2010 17:12:36 -0700 [thread overview]
Message-ID: <20101007001236.GY14666@outflux.net> (raw)
In-Reply-To: <20101006225104.GA21013@suse.de>
Hi Greg,
On Wed, Oct 06, 2010 at 03:51:04PM -0700, Greg KH wrote:
> Nice catch, but I don't think that the dev pointer can ever be NULL
> here.
Yeah, I didn't think so either, but figured it was best to fix it anyway.
-Kees
--
Kees Cook
Ubuntu Security Team
prev parent reply other threads:[~2010-10-07 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 22:39 [PATCH] staging: fix possible use-before-NULL-check crash Kees Cook
2010-10-06 22:51 ` Greg KH
2010-10-07 0:12 ` Kees Cook [this message]
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=20101007001236.GY14666@outflux.net \
--to=kees.cook@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=stefan.ringel@arcor.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.