From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Cc: Mike Snitzer <snitzer@redhat.com>,
Mike Christie <michaelc@cs.wisc.edu>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 1/8] dm-mpath, scsi_dh: don't let dm detach device handlers
Date: Mon, 11 May 2015 14:51:59 +0200 [thread overview]
Message-ID: <5550A5EF.1060904@suse.de> (raw)
In-Reply-To: <1431283260-13406-2-git-send-email-hch@lst.de>
On 05/10/2015 08:40 PM, Christoph Hellwig wrote:
> While allowing dm-mpath to attach device handlers is a functionality we need
> for backwards compatibility reason there is no reason to reference count
> them and detach them if dm-mpath stops using the device for some reason.
>
> If the device handler works for the given device it can just stay attached,
> and we can take the retain_hw_handler codepath.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
[ .. ]
>
> @@ -597,20 +595,14 @@ static struct pgpath *parse_path(struct dm_arg_set *as, struct path_selector *ps
> }
>
> if (m->hw_handler_name) {
> - /*
> - * Increments scsi_dh reference, even when using an
> - * already-attached handler.
> - */
> r = scsi_dh_attach(q, m->hw_handler_name);
> if (r == -EBUSY) {
> - /*
> - * Already attached to different hw_handler:
> - * try to reattach with correct one.
> - */
> - scsi_dh_detach(q);
> - r = scsi_dh_attach(q, m->hw_handler_name);
> + char b[BDEVNAME_SIZE];
> +
Whitespace error ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (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
next prev parent reply other threads:[~2015-05-11 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 18:40 integrate scsi_dh better into the scsi core V2 Christoph Hellwig
2015-05-10 18:40 ` [PATCH 1/8] dm-mpath, scsi_dh: don't let dm detach device handlers Christoph Hellwig
2015-05-11 12:51 ` Hannes Reinecke [this message]
2015-05-12 8:10 ` Christoph Hellwig
2015-05-10 18:40 ` [PATCH 2/8] dm-mpath, scsi_dh: request scsi_dh modules in scsi_dh, not dm-mpath Christoph Hellwig
2015-05-10 18:40 ` [PATCH 3/8] scsi_dh: move to drivers/scsi Christoph Hellwig
2015-05-10 18:40 ` [PATCH 4/8] scsi_dh: integrate into the core SCSI code Christoph Hellwig
2015-05-10 18:40 ` [PATCH 5/8] scsi_dh: move device matching to the core code Christoph Hellwig
2015-05-10 18:40 ` [PATCH 6/8] scsi_dh: kill struct scsi_dh_data Christoph Hellwig
2015-05-10 18:40 ` [PATCH 7/8] scsi_dh: add a common helper to get a scsi_device from a request_queue Christoph Hellwig
2015-05-10 18:41 ` [PATCH 8/8] scsi_dh: don't allow to detach device handlers at runtime Christoph Hellwig
2015-05-18 17:28 ` integrate scsi_dh better into the scsi core V2 Christoph Hellwig
2015-05-18 17:36 ` Hannes Reinecke
2015-06-19 13:06 ` Hannes Reinecke
2015-06-19 13:17 ` Christoph Hellwig
2015-06-19 13:20 ` Hannes Reinecke
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=5550A5EF.1060904@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michaelc@cs.wisc.edu \
--cc=snitzer@redhat.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