From: Christoph Hellwig <hch@lst.de>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: Christoph Hellwig <hch@lst.de>,
Matt_Domsch@Dell.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fusion: streamline ->slave_alloc/->slave_destroy
Date: Tue, 26 Oct 2004 18:12:12 +0200 [thread overview]
Message-ID: <20041026161212.GA28795@lst.de> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57053AF0AF@exa-atlanta>
On Tue, Oct 26, 2004 at 12:02:13PM -0400, Moore, Eric Dean wrote:
> On Tuesday, October 26, 2004 6:55 AM, Christoph Hellwig wrote:
> > That was not just with my patch but with your new monster
> > update, right?
> >
> > It contains this totally bogus line:
> >
> > +
> > + /* remove the device from our
> > internal data structures */
> > + if(hd->Targets[pScsiReq->TargetID] != NULL) {
> > + mptscsih_slave_destroy(sc->device);
> > + }
> > +
> >
> > in mptscsih_io_done
> >
>
> This code was added by request of the megalib team, and Matt Domsch.
> This was added for support of hot swap in non-raid environment.
> The IOCSTATUS=MPI_IOCSTATUS_SCSI_DEVICE_NOT_THERE will be received
> when drive has been removed, and this code was added to automatically
> remove the instance of the device. Thus an application such as megalib
> would
> know real time that devices have been removed, instead of waiting on a scsi
> bus scan.
but this is buggy. You must tell the scsi midlayer to perform a removal
with scsi_remove_device, which will call back into ->slave_destroy. If
you just call mptscsih_slave_destroy there's still a midlayer
scsi_device object, but your internal datastructures are dangling.
next prev parent reply other threads:[~2004-10-26 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 16:02 [PATCH] fusion: streamline ->slave_alloc/->slave_destroy Moore, Eric Dean
2004-10-26 16:12 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 18:39 Moore, Eric Dean
2004-10-21 9:09 ` Christoph Hellwig
2004-10-26 12:55 ` Christoph Hellwig
2004-10-06 18:25 Moore, Eric Dean
2004-10-09 14:51 ` Christoph Hellwig
2004-10-02 8:23 Christoph Hellwig
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=20041026161212.GA28795@lst.de \
--to=hch@lst.de \
--cc=Emoore@lsil.com \
--cc=Matt_Domsch@Dell.com \
--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;
as well as URLs for NNTP newsgroup(s).