From: Mike Christie <michaelc@cs.wisc.edu>
To: Bhanu Prakash Gollapudi <bprakash@broadcom.com>
Cc: Joe Eykholt <jeykholt@cisco.com>,
"devel@open-fcoe.org" <devel@open-fcoe.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Open-FCoE] deadlock during fc_remove_host
Date: Wed, 20 Apr 2011 22:21:51 -0500 [thread overview]
Message-ID: <4DAFA2CF.2080102@cs.wisc.edu> (raw)
In-Reply-To: <4DAF9C15.1010808@cs.wisc.edu>
On 04/20/2011 09:53 PM, Mike Christie wrote:
> Is the reason that rport b's terminate_rport_io has not been called,
> because that workqueue is queued behind rport a's workqueue and rport
> b's workqueue function is not called? If so, have you tested this with
> the current upstream kernel?
Oh wait, I think you also need to change the fc class to use
alloc_workqueue instead of create_singlethread_workqueue.
next prev parent reply other threads:[~2011-04-21 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 0:24 deadlock during fc_remove_host Bhanu Prakash Gollapudi
2011-04-21 2:53 ` Mike Christie
2011-04-21 3:21 ` Mike Christie [this message]
2011-04-22 5:47 ` [Open-FCoE] " Bhanu Prakash Gollapudi
2011-04-21 5:32 ` Bhanu Prakash Gollapudi
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=4DAFA2CF.2080102@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=bprakash@broadcom.com \
--cc=devel@open-fcoe.org \
--cc=jeykholt@cisco.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).