On Wed, Mar 12 2008 at 19:00 +0200, James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
