From: Adrian Bunk <bunk@kernel.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: yokota@netlab.is.tsukuba.ac.jp, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] nsp32_restart_autoscsi(): remove error check
Date: Wed, 24 Oct 2007 18:54:34 +0200 [thread overview]
Message-ID: <20071024165434.GZ30533@stusta.de> (raw)
In-Reply-To: <1193244072.3396.17.camel@localhost.localdomain>
On Wed, Oct 24, 2007 at 12:41:12PM -0400, James Bottomley wrote:
> On Wed, 2007-10-24 at 18:25 +0200, Adrian Bunk wrote:
> > The Coverity checker noted that we'll anyway Oops later when we ran into
> > this condition - and the error check didn't prevent that.
> >
> > Considering that the error condition shouldn't be possible, and we are
> > not able to handle it easily, this patch simply removes the pointless
> > error check.
>
> This is the one where I said I don't like the fact that you're removing
> the explanatory message that's printed before we crash. if you want to
> shut coverity up and stop sending the patch, I'm happy adding a BUG();
> after the nsp32_msg().
Sorry, I missed your answer when resending since it was in a different
thread.
I'm still not convinced we really need the nsp32_msg() here but you are
the maintainer and it's not a big deal anyway
A BUG() would IMHO be similarly pointless as the nsp32_msg() at this
point and there's no value in changing code only for the sake of the
Coverity checker.
> James
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
next prev parent reply other threads:[~2007-10-24 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:25 [RFC: 2.6 patch] nsp32_restart_autoscsi(): remove error check Adrian Bunk
2007-10-24 16:41 ` James Bottomley
2007-10-24 16:54 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 19:33 Adrian Bunk
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=20071024165434.GZ30533@stusta.de \
--to=bunk@kernel.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yokota@netlab.is.tsukuba.ac.jp \
/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.