public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@parallels.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Use queuedata accessors for device handler
Date: Mon, 22 Aug 2011 17:31:15 +0200	[thread overview]
Message-ID: <4E527643.601@suse.de> (raw)
In-Reply-To: <20110822144505.GA5705@infradead.org>

On 08/22/2011 04:45 PM, Christoph Hellwig wrote:
> On Mon, Aug 22, 2011 at 03:35:43PM +0200, Hannes Reinecke wrote:
>>
>> Starting multipath on a cciss device will cause a kernel
>> warning to be triggered. Problem is that we're using the
>> ->queuedata field of the request_queue to dereference the
>> scsi device; however, for other (non-SCSI) devices this
>> points to a totally different structure.
>> So we should rather be using accessors here to make
>> sure ->queuedata points to a valid sdev.
>
> How do we match to attach a scsi device handler to a non-scsi queue?
> I suspect that is the fundamental issue that needs addressing.
>
We don't. SCSI device handler are only for SCSI devices, not block 
devices. But scsi_dh_attach() and scsi_dh_detach() is called from 
dm-mpath.c:parse_path(), and this doesn't have any idea about the 
underlying device type.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-08-22 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 13:35 [PATCH] Use queuedata accessors for device handler Hannes Reinecke
2011-08-22 14:45 ` Christoph Hellwig
2011-08-22 15:31   ` Hannes Reinecke [this message]

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=4E527643.601@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@parallels.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    /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