All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Anton Blanchard <anton@samba.org>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.14-rc1] sym scsi boot hang
Date: Thu, 15 Sep 2005 09:56:13 -0400	[thread overview]
Message-ID: <1126792573.4821.18.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509141716410.8011-100000@iolanthe.rowland.org>

On Wed, 2005-09-14 at 17:33 -0400, Alan Stern wrote:
> On Wed, 14 Sep 2005, James Bottomley wrote:
> > Yes ... really the only case for unprep is when we've partially released
> > the command (like in scsi_io_completion) where we need to tear the rest
> > of it down.
> 
> In other words, in scsi_requeue_command and nowhere else.

Pretty much, yes.

> Or will be prepared for the first time, as in scsi_execute.  As far as I 
> can tell, a new struct request is not set to all 0's.  So if you queue a 
> request with REQ_SPECIAL set and you fail to clear req->special, you're in 
> trouble.  Do you have any idea why this hasn't been causing errors all 
> along?

That's true, it's not.  However ll_rq_blk.c:rq_init() clears req-
>special (and initialises all other important fields).

> Okay, then how does this patch look (moved the routine over to where it 
> gets used, plus two real changes)?

Well ... under pressure to fix this in -mm, I already commited a version
to rc-fixes.  What I did was fully reverse the changes to the
scsi_insert_queue() [the patch I sent Anton].  We can move the unprep
function if you feel strongly about it, but I'm also happy to keep it
where it is.

James



  reply	other threads:[~2005-09-15 13:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 12:48 [2.6.14-rc1] sym scsi boot hang Dipankar Sarma
2005-09-13 13:17 ` Anton Blanchard
2005-09-13 14:29   ` Anton Blanchard
2005-09-13 16:35     ` James Bottomley
2005-09-13 16:47       ` Anton Blanchard
2005-09-13 17:32         ` James Bottomley
2005-09-13 17:13           ` Anton Blanchard
2005-09-13 17:33           ` Dipankar Sarma
2005-09-14  8:06       ` Anton Blanchard
2005-09-14 15:49         ` Alan Stern
2005-09-14 16:52           ` Mike Christie
2005-09-14 16:53             ` Mike Christie
2005-09-14 20:35           ` James Bottomley
2005-09-14 16:57         ` James Bottomley
2005-09-14 20:19           ` Alan Stern
2005-09-14 20:44             ` James Bottomley
2005-09-14 21:33               ` Alan Stern
2005-09-15 13:56                 ` James Bottomley [this message]
2005-09-15 14:13                   ` Alan Stern
2005-09-15 17:52                   ` Alan Stern
2005-09-16 10:28           ` Anton Blanchard

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=1126792573.4821.18.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=anton@samba.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.