From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH] for Deadlock in transport_fc
Date: Thu, 09 Jun 2005 16:11:41 +0200 [thread overview]
Message-ID: <42A84E1D.5060607@fujitsu-siemens.com> (raw)
In-Reply-To: <9BB4DECD4CFE6D43AA8EA8D768ED51C201AC67@xbl3.ad.emulex.com>
James.Smart@Emulex.Com wrote:
>
>>BTW: at least once when we disconnected one target and
>>connected the other
>>without waiting for nodev_tmo, we saw the situation, that the
>>new target was
>>accessible, while sysfs still showed us the old wwpn.
>
>
> We ought to track this further offline. There's more detail I'd like to
> get from you to ensure there isn't an error here.
>
We'll try to reproduce this. If we succeed, we will let you know the
recipe.
Bodo
next prev parent reply other threads:[~2005-06-09 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 14:05 [PATCH] for Deadlock in transport_fc James.Smart
2005-06-09 14:11 ` Bodo Stroesser [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 2:56 James.Smart
2005-06-09 13:47 ` Bodo Stroesser
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=42A84E1D.5060607@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=James.Smart@Emulex.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