linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: sekharan@linux.vnet.ibm.com,
	James Bottomley <James.Bottomley@HansenPartnership.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 14:47:14 -0400	[thread overview]
Message-ID: <4A54E9B2.3030309@redhat.com> (raw)
In-Reply-To: <20090708184039.GA11348@infradead.org>

On 07/08/2009 02:40 PM, Christoph Hellwig wrote:
> On Wed, Jul 08, 2009 at 02:33:01PM -0400, Peter Jones wrote:
>> This behavior is conditional on the module parameter
>> scsi_mod.target_modalias_has_vendor, which has its default set by the
>> enabling or disabling of CONFIG_SCSI_TARGET_MODALIAS_WITH_ID .
> 
> Sorry, but that's really stupid.  If people have the arrays that have
> device handlers there are two possible cases:
> 
>  - just a single port configured on the array. In this case the device
>    handlers are useless but also completely unharmful.
>  - multiple ports configured on the array.  In this case we desperately
>    want the device handlers loaded early so that we do the right thing
>    for the inactive ports and avoid the horrible probing delays, not
>    matter if we actually do end up using multipath later or no.
> 
> No need to make this configurable.  If people really do not want the
> handler (e.g. becuase the may end up beeing buggy for a new array
> matching the old idea) they can just blacklist it in the modules
> configuration.

Which is what I had in mind when I wrote the original version of this,
but which James does not agree with.

-- 
        Peter

  reply	other threads:[~2009-07-08 18:47 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
2009-07-08 18:33                   ` Peter Jones
2009-07-08 18:40                     ` Christoph Hellwig
2009-07-08 18:47                       ` Peter Jones [this message]
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=4A54E9B2.3030309@redhat.com \
    --to=pjones@redhat.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=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;
as well as URLs for NNTP newsgroup(s).