From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Peter Jones <pjones@redhat.com>,
linux-scsi@vger.kernel.org, michaelc@cs.wisc.edu, hare@suse.de
Subject: Re: [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted
Date: Wed, 08 Jul 2009 11:21:00 -0700 [thread overview]
Message-ID: <1247077260.1200.9.camel@chandra-ubuntu> (raw)
In-Reply-To: <20090708155808.GA31204@infradead.org>
On Wed, 2009-07-08 at 11:58 -0400, Christoph Hellwig wrote:
> On Tue, Jul 07, 2009 at 12:36:41PM -0700, Chandra Seetharaman wrote:
> > I do not know of all the out-of-tree multipath solutions and how they
> > behave and at what layer they interact. In effect, I haven't tested
> > hardware handler with other multipath solutions.
>
> It doesn't matter anyway. We've never cared about these out of tree
> problems and they'll have to find a way by themselves to deal with any
> changes we do to offer better multipath support upstream.
Agree.
One simple way the out-of-tree multipath solutions can circumvent this
feature is by blacklisting the hardware handler modules in their
modprobe.conf file.
>
> --
> 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:[~2009-07-08 18:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 18:06 [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted Chandra Seetharaman
2009-04-27 18:06 ` [PATCH 1/3] scsi_dh: Add modalias support for SCSI targets Chandra Seetharaman
2009-04-27 18:06 ` [PATCH 2/3] scsi_dh: Change scsi device handler modules to utilize modalias Chandra Seetharaman
2009-04-27 18:06 ` [PATCH 3/3] scsi_dh: Workaround a race condition in module insertion Chandra Seetharaman
2009-06-15 18:29 ` [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted Peter Jones
2009-06-15 23:14 ` Chandra Seetharaman
2009-06-18 22:48 ` James Bottomley
2009-06-19 18:58 ` Peter Jones
2009-06-26 13:56 ` Peter Jones
2009-07-07 17:12 ` James Bottomley
2009-07-07 17:51 ` Peter Jones
2009-07-07 18:14 ` James Bottomley
2009-07-07 19:36 ` Chandra Seetharaman
2009-07-08 15:53 ` [PATCH 0/3] scsi_dh: Make scsi device handler modulesautomatically inserted berthiaume_wayne
2009-07-08 18:28 ` Chandra Seetharaman
2009-07-08 15:58 ` [PATCH 0/3] scsi_dh: Make scsi device handler modules automatically inserted Christoph Hellwig
2009-07-08 18:21 ` Chandra Seetharaman [this message]
2009-07-08 18:33 ` Peter Jones
2009-07-08 18:40 ` Christoph Hellwig
2009-07-08 18:47 ` Peter Jones
2009-07-15 20:33 ` Chandra Seetharaman
2009-07-16 1:16 ` James Bottomley
2009-07-17 1:01 ` Chandra Seetharaman
2009-07-17 4:19 ` James Bottomley
2009-07-17 14:14 ` Peter Jones
2009-07-17 16:45 ` James Bottomley
2009-07-17 17:13 ` Peter Jones
2009-06-19 19:37 ` Chandra Seetharaman
2009-07-06 22:30 ` Chandra Seetharaman
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 1:36 Chandra Seetharaman
2009-03-18 11:31 ` 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=1247077260.1200.9.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pjones@redhat.com \
--cc=sekharan@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