public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux Scsi Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: One more change pushed to bk tree
Date: Fri, 22 Nov 2002 17:22:47 -0500	[thread overview]
Message-ID: <20021122222247.GB18664@redhat.com> (raw)
In-Reply-To: <20021122204538.A10657@infradead.org>

On Fri, Nov 22, 2002 at 08:45:38PM +0000, Christoph Hellwig wrote:
> On Fri, Nov 22, 2002 at 01:36:03PM -0500, Doug Ledford wrote:
> > Like last time, this has been through a full compile test, but not a boot 
> > test.  I'm heading up to the office next so the boot test will come 
> > shortly.  But, because it touches lots of files, again, I thought I would 
> > go ahead and push it up for people to see.  If there are no objections to 
> > this or my previous patches, then once the boot test is complete and I'm 
> > satisfied things are working properly, I'll push the whole lot to Linus 
> > (which will necessarily include the scsi-misc-2.5 changes because they are 
> > in my tree as well).
> 
> Heh, now you managed to get stuff commited before me and I need to merge
> up :)  But your changes help me a lot in fact so I surely won't complain.

Quoting from my email yesterday:

It's a race Charlie Brown!

;-)

> Two comments: 
> 
>  o as you already had to change all callers of host->host_queue/
>    host->my_devices could you add a lock to properly protect it?  That's
>    pretty important for hotplugging/etc.. (like the fc hotplug patch
>    from montavista)

I'm actually thinking that the locking of the devices is not needed as 
long as the next step is to A) make sure that all people walking the 
my_devices list already are holding a reference to the parent host vi 
host_get_*() and B) that proper locking for hosts is actually implemented 
in the host_get*() routines instead of the stub comments that are there 
now.

>  o what's the reason in continuing after an error from scsi_add_host
>    in scsi_add_host?  IMHO it doesn't make much sense to continue the
>    bus scan in that case.

There's no guarantee that devices later on in the chain will fail to 
attach, so I saw little reason to leave things half done.  If they all 
fail after the first failure, then we are no worse off then by bailing 
early, but if some actually succeed then we are better off.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2002-11-22 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 18:36 One more change pushed to bk tree Doug Ledford
2002-11-22 20:45 ` Christoph Hellwig
2002-11-22 22:22   ` Doug Ledford [this message]
2002-11-22 22:56     ` Christoph Hellwig
2002-11-22 22:24 ` Doug Ledford
2002-11-22 23:43   ` Doug Ledford
2002-11-22 23:56 ` Patrick Mansfield
2002-11-23  2:45   ` Doug Ledford
2002-11-25 17:02     ` Luben Tuikov
2002-11-25 19:45     ` Patrick Mansfield

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=20021122222247.GB18664@redhat.com \
    --to=dledford@redhat.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