From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] scsi_lib: don't decrement busy counters when inserting commands
Date: Sun, 04 Jan 2009 14:53:28 -0600 [thread overview]
Message-ID: <496121C8.4040205@cs.wisc.edu> (raw)
In-Reply-To: <1230914541.3304.9.camel@localhost.localdomain>
James Bottomley wrote:
> On Tue, 2008-12-16 at 23:55 -0600, michaelc@cs.wisc.edu wrote:
>> From: Mike Christie <michaelc@cs.wisc.edu>
>>
>> This patch fixes a regression in scsi-misc introduced with:
>> 312efe5efcdb02d604ea37a41d965f32ca276d6a
>> [SCSI] simplify scsi_io_completion().
>>
>> The problem is that in previous kernels scsi_io_completion would call
>> scsi_requeue_command, but now it can call scsi_queue_insert for
>> something like a UNIT_ATTENTION (for netapp targets we get
>> UNIT_ATTENTION when restarting a iscsi session). And scsi_queue_insert
>> will call scsi_device_unbusy, but in the scsi_io_completion code path
>> scsi_finish_command has already called this so we now end up
>> with invalid host, target and device busy values.
>>
>> Patch was made over scsi-misc.
>
> This is a bad bug, but not quite the way I'd like to fix it. Whether
> the queue should be unbusied or not is really separate from the block
> action, so it should have its own flag (plus it's not really a flag many
> people should be using). Since, really, the wrong use is confined to
> the defining file, how about this:
>
Patch fixed my problem here. Thanks.
next prev parent reply other threads:[~2009-01-04 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 5:55 [PATCH] scsi_lib: don't decrement busy counters when inserting commands michaelc
2008-12-18 9:03 ` Andrew Vasquez
2009-01-02 16:42 ` James Bottomley
2009-01-03 3:39 ` Alan Stern
2009-01-04 20:53 ` Mike Christie [this message]
2009-01-05 23:28 ` Andrew Vasquez
2009-01-06 1:56 ` James Bottomley
2009-01-06 7:01 ` Andrew Vasquez
2009-01-06 19:15 ` James Bottomley
2009-01-06 19:48 ` Andrew Vasquez
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=496121C8.4040205@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--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.