public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: akpm@linux-foundation.org, linux-scsi@vger.kernel.org,
	yokota@netlab.is.tsukuba.ac.jp
Subject: Re: [patch 13/30] nsp32_restart_autoscsi(): remove error check
Date: Sat, 11 Aug 2007 04:25:39 +0200	[thread overview]
Message-ID: <20070811022539.GD22213@stusta.de> (raw)
In-Reply-To: <1186794232.6334.21.camel@localhost.localdomain>

On Fri, Aug 10, 2007 at 09:03:52PM -0400, James Bottomley wrote:
> 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.

"Target or Lun is invalid" isn't a precise problem description either.

But the main point is:

An Oops indicates a programming error in the kernel (or kernel 
corruption), and for this purpose an Oops is a good error message.

We can't put printk()'s in front of all pointer dereferences in the 
kernel.

Is there any legal way how any of these could be NULL at this point?
My impression was there isn't.
But if there is we don't need only a printk(), we'd need an error 
handling that returns from the function without Oops'ing plus an error 
handling in the caller.

> 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


      reply	other threads:[~2007-08-11  2:25 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
2007-08-11  2:25   ` 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=20070811022539.GD22213@stusta.de \
    --to=bunk@stusta.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox