public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] add back single_lun support
Date: 05 Feb 2003 17:14:00 -0600	[thread overview]
Message-ID: <1044486842.1773.89.camel@mulgrave> (raw)
In-Reply-To: <20030205145104.A6169@beaverton.ibm.com>

On Wed, 2003-02-05 at 16:51, Patrick Mansfield wrote:
> This patch against the current scsi-misc-2.5 adds back the check for the
> single_lun case.
> 
> I compiled and booted with this applied but don't have any devices (i.e.
> CD ROM changer) for testing.
> 
> --- 1.66/drivers/scsi/scsi_lib.c	Wed Feb  5 08:33:15 2003
> +++ edited/drivers/scsi/scsi_lib.c	Tue Feb 11 14:27:08 2003
> @@ -787,6 +787,22 @@
>  	return ret;
>  }
>  
> +/*
> + * The target associated with myself can only handle one active command at
> + * a time. Scan through all of the luns on the same target as myself,
> + * return 1 if any are active.
> + */
> +static int check_all_luns(struct scsi_device *myself)
> +{
> +	struct scsi_device *sdev;
> +
> +	list_for_each_entry(sdev, &myself->same_target_siblings,
> +			    same_target_siblings)
> +		if (atomic_read(&sdev->device_active))
> +			return 1;
> +	return 0;
> +}
> +

I don't see device_active getting set anywhere.

shouldn't we just dump device_active in favour of a non-zero check of
device_busy (it's all done under the queue lock, anyway).

James



  reply	other threads:[~2003-02-05 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 22:51 [PATCH] add back single_lun support Patrick Mansfield
2003-02-05 23:14 ` James Bottomley [this message]
2003-02-06  1:16   ` Patrick Mansfield
2003-02-06 14:27   ` Christoph Hellwig

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=1044486842.1773.89.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    /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