From: Adrian Bunk <bunk@stusta.de>
To: "Ed L. Cashin" <ecashin@coraid.com>
Cc: Alan Cox <alan@redhat.com>, Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.19 patch] drivers/block/aoe/aoedev.c: fix NULL dereference
Date: Wed, 1 Nov 2006 19:38:40 +0100 [thread overview]
Message-ID: <20061101183840.GG27968@stusta.de> (raw)
In-Reply-To: <20061101163628.GC20570@coraid.com>
On Wed, Nov 01, 2006 at 11:36:28AM -0500, Ed L. Cashin wrote:
> On Wed, Nov 01, 2006 at 01:40:25AM +0100, Adrian Bunk wrote:
> > This patch fixes a NULL dereference introduced by
> > commit e407a7f6cd143b3ab4eb3d7e1cf882e96b710eb5:
> >
> > This quite unusual error handling through a switch introduces NULL
> > dereferences if exactly one of the two k{c,z}alloc's failed.
>
> Hmm. If exactly one of the two fails, then the value of the switch
> conditional is 1 (well, certainly not zero). It will jump over the
> zero case, and there's a return in the default case, so I'm having
> trouble seeing the danger.
>
> What exactly is Coverity saying? That would be interesting to know.
The Coverity checker was wrong in this case, and I didn't spot it when
checking since the code is really confusing.
> Ed L Cashin <ecashin@coraid.com>
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-11-01 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 0:40 [2.6.19 patch] drivers/block/aoe/aoedev.c: fix NULL dereference Adrian Bunk
2006-11-01 16:36 ` Ed L. Cashin
2006-11-01 18:38 ` Adrian Bunk [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=20061101183840.GG27968@stusta.de \
--to=bunk@stusta.de \
--cc=alan@redhat.com \
--cc=ecashin@coraid.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.