public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: James.Bottomley@SteelEye.com
Cc: aab@cichlid.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: Oops in scsi_send_eh_cmnd 2.6.21-rc5-git6,7,10,13
Date: Thu, 05 Apr 2007 17:15:06 -0700 (PDT)	[thread overview]
Message-ID: <20070405.171506.125894469.davem@davemloft.net> (raw)
In-Reply-To: <1175817739.3714.43.camel@mulgrave.il.steeleye.com>

From: James Bottomley <James.Bottomley@SteelEye.com>
Date: Thu, 05 Apr 2007 19:02:19 -0500

> On Thu, 2007-04-05 at 15:36 -0700, David Miller wrote:
> > From: Andrew Burgess <aab@cichlid.com>
> > Date: Thu, 5 Apr 2007 15:13:27 -0700
> > 
> > > David, do you see any other problems with scsi_send_eh_cmnd?
> > > 
> > > I've switched back to 2.6.18 which seems to not oops 
> > > and am happy to try patches.
> > 
> > Does 2.6.20 with my patch OOPS too?  Does reverting my patch
> > make the oops go away?
> > 
> > If reverting my patch makes the OOPS go away, we need to
> > verify if page_address() is returning crap for some reason
> > or the length is wrong.
> 
> Assuming this does turn out to be the problem, we should just junk the
> page allocation ... it's completely unnecessary; when the slab allocated
> commands were done, we made sure the actual sense_buffer is at the
> correct location, so this should be the final fix:

This won't work I believe.

There are cases that use smaller sense buffers than the minimum
specified by the SCSI layer.

One example is that do_sr_ioctl() stuff when the cgc passed
in has a sense buffer.  That will only be as large as a
"struct request_sense".

I'm pretty sure that's one of the reasons why we cons up a local sense
buffer in this EH code.

So we could walk past the end of that and corrupt memory with
your patch.

  reply	other threads:[~2007-04-06  0:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 22:13 Oops in scsi_send_eh_cmnd 2.6.21-rc5-git6,7,10,13 Andrew Burgess
2007-04-05 22:36 ` David Miller
2007-04-06  0:02   ` James Bottomley
2007-04-06  0:15     ` David Miller [this message]
2007-04-06  0:51       ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2007-04-06  2:21 Andrew Burgess
2007-04-06 13:44 ` James Bottomley
2007-04-06 15:12 Andrew Burgess
2007-04-06 15:27 ` James Bottomley
2007-04-06 18:32   ` David Miller
2007-04-06 21:35     ` James Bottomley
2007-04-06 15:51 Andrew Burgess
2007-04-06 16:14 ` James Bottomley
2007-04-06 16:32   ` Douglas Gilbert
2007-04-06 16:47     ` James Bottomley
2007-04-06 18:18 Andrew Burgess

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=20070405.171506.125894469.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=aab@cichlid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox