From: James Bottomley <James.Bottomley@SteelEye.com>
To: akpm@linux-foundation.org
Cc: linux-scsi@vger.kernel.org, bunk@stusta.de,
yokota@netlab.is.tsukuba.ac.jp
Subject: Re: [patch 13/30] nsp32_restart_autoscsi(): remove error check
Date: Fri, 10 Aug 2007 21:03:52 -0400 [thread overview]
Message-ID: <1186794232.6334.21.camel@localhost.localdomain> (raw)
In-Reply-To: <200708102150.l7ALoeZw011354@imap1.linux-foundation.org>
On Fri, 2007-08-10 at 14:50 -0700, akpm@linux-foundation.org wrote:
> From: Adrian Bunk <bunk@stusta.de>
>
> 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.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> Cc: <yokota@netlab.is.tsukuba.ac.jp>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/scsi/nsp32.c | 4 ----
> 1 files changed, 4 deletions(-)
>
> diff -puN drivers/scsi/nsp32.c~nsp32_restart_autoscsi-remove-error-check drivers/scsi/nsp32.c
> --- a/drivers/scsi/nsp32.c~nsp32_restart_autoscsi-remove-error-check
> +++ a/drivers/scsi/nsp32.c
> @@ -1905,10 +1905,6 @@ static void nsp32_restart_autoscsi(struc
>
> nsp32_dbg(NSP32_DEBUG_RESTART, "enter");
>
> - if (data->cur_target == NULL || data->cur_lunt == NULL) {
> - nsp32_msg(KERN_ERR, "Target or Lun is invalid");
> - }
> -
I disagree pretty strongly with this ... you're not removing an error
check, you're removing a warning printk. Before the driver would say
what the problem is and oops. After, it will oops and you won't
necessarily know why. I think that's a retrograde step.
James
next prev parent reply other threads:[~2007-08-11 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:50 [patch 13/30] nsp32_restart_autoscsi(): remove error check akpm
2007-08-11 1:03 ` James Bottomley [this message]
2007-08-11 2:25 ` 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=1186794232.6334.21.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox