mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mike Qiu <qiudayu@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	haokexin@gmail.com, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 1/2] libata: Fix scsi_host can_queue issue in ata_qc_new()
Date: Tue, 22 Jul 2014 11:42:44 -0400	[thread overview]
Message-ID: <20140722154244.GJ13851@htj.dyndns.org> (raw)
In-Reply-To: <1406040619-1722-1-git-send-email-qiudayu@linux.vnet.ibm.com>

Hello,

(cc'ing Dan)

On Tue, Jul 22, 2014 at 10:50:19AM -0400, Mike Qiu wrote:
> The can_queue in scsi_host can be more than ATA_MAX_QUEUE (32),
> for example, in ipr, it can be 100 or more.
> 
> Also, some drivers, like ipr driver, haven't filled the field
> scsi_host in ata_port, and will lead a call trace, so add
> check for that.
> 
> Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
> ---
>  drivers/ata/libata-core.c | 15 ++++-----------
>  1 file changed, 4 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 259d879..a5b9c70 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4734,7 +4734,10 @@ static struct ata_queued_cmd *ata_qc_new(struct ata_port *ap)
>  	struct ata_queued_cmd *qc = NULL;
>  	unsigned int i, tag, max_queue;
>  
> -	max_queue = ap->scsi_host->can_queue;
> +	if (ap->scsi_host && ap->scsi_host->can_queue <= ATA_MAX_QUEUE)
> +		max_queue = ap->scsi_host->can_queue;
> +	else
> +		max_queue = ATA_MAX_QUEUE;
>  
>  	/* no command while frozen */
>  	if (unlikely(ap->pflags & ATA_PFLAG_FROZEN))
> @@ -6109,16 +6112,6 @@ int ata_host_register(struct ata_host *host, struct scsi_host_template *sht)
>  {
>  	int i, rc;
>  
> -	/*
> -	 * The max queue supported by hardware must not be greater than
> -	 * ATA_MAX_QUEUE.
> -	 */
> -	if (sht->can_queue > ATA_MAX_QUEUE) {
> -		dev_err(host->dev, "BUG: the hardware max queue is too large\n");
> -		WARN_ON(1);
> -		return -EINVAL;
> -	}
> -

So, ummm, I really don't like that we're adding the conditionals to
the hot path (yeah, its implementation is slow but still).  Maybe we
need to store the chosen queue depth after all?  Dan?

Thanks.

-- 
tejun

  reply	other threads:[~2014-07-22 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 14:50 Mike Qiu
2014-07-22 15:42 ` Tejun Heo [this message]
2014-07-23  2:10   ` Mike Qiu
2014-07-25 17:01     ` Dan Williams

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=20140722154244.GJ13851@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=haokexin@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiudayu@linux.vnet.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

all inboxes | Powered by JetHome®