From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
linux-scsi <linux-scsi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] isd200: Use scsi_get_cmnd for the extra translation command
Date: Wed, 12 Mar 2008 19:27:41 +0200 [thread overview]
Message-ID: <47D8128D.3050405@panasas.com> (raw)
In-Reply-To: <1205341209.2941.116.camel@localhost.localdomain>
On Wed, Mar 12 2008 at 19:00 +0200, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Wed, 2008-03-12 at 17:15 +0200, Boaz Harrosh wrote:
>> James
>> please comment on the use of DID_REQUEUE as return status for
>> the command in case of failure to allocate the extra command the first
>> time.
>
> I'm afraid it won't work. If you get a NULL return from
> scsi_get_command, it means that the command you already have was likely
> taken from the host free_list. If that command is in the memory
> clearing writeout path and we don't have any returning commands to
> replace the free_list, the system is now deadlocked.
>
> James
>
I'm not sure you are right. Please bear in mind that for isd200 an host
has exactly one device. Now this *very first command* is some kind of
INQUIRY in the discovery process, so it cannot be mounted for SWAP as yet.
so it cannot be in the "clearing writeout path". Any kind of error on this
first command will just result in an "empty" device, No?
I guess a newly mounted device on a memory starved system has lots of places
to fail before and after this point in time.
Boaz
next prev parent reply other threads:[~2008-03-12 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 15:15 [PATCH] isd200: Use scsi_get_cmnd for the extra translation command Boaz Harrosh
[not found] ` <47D7F397.4070903-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2008-03-12 16:00 ` Boaz Harrosh
2008-03-12 17:00 ` James Bottomley
2008-03-12 17:27 ` Boaz Harrosh [this message]
[not found] ` <47D8128D.3050405-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2008-03-13 16:47 ` James Bottomley
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=47D8128D.3050405@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--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.