From: James Bottomley <James.Bottomley@SteelEye.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fc_transport: fix sysfs deadlock on vport delete
Date: Tue, 22 May 2007 10:42:12 -0500 [thread overview]
Message-ID: <1179848532.3738.15.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1177692740.26526.3.camel@localhost.localdomain>
On Fri, 2007-04-27 at 12:52 -0400, James Smart wrote:
> When the vport attribute "delete" is used to delete the vport, sysfs
> deadlocks waiting for the write to complete, which is waiting for the
> sysfs teardown to complete. Moved this effort to a work_q element.
>
> Took the opportunity to make some other cosmetic changes:
> - removed tabs in Doc file - replaced with expanded spaces
> - minor copyright text and author text updates
> - removed a bunch of trailing whitespace
This one rejects against scsi-misc, could you reroll
(I suspect because the prior vport patch had spacing errors which git
makes me fix before I commit).
James
prev parent reply other threads:[~2007-05-22 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 16:52 [PATCH] fc_transport: fix sysfs deadlock on vport delete James Smart
2007-05-22 15:42 ` James Bottomley [this message]
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=1179848532.3738.15.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.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