From: "Love, Robert W" <robert.w.love@intel.com>
To: "bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 42918] fcoe: Enabling VN2VN mode triggers a circular locking complaint
Date: Thu, 15 Mar 2012 01:28:18 +0000 [thread overview]
Message-ID: <4F6145B1.30604@intel.com> (raw)
In-Reply-To: <201203150121.q2F1Ln8l003505@bugzilla.kernel.org>
On 03/14/2012 06:21 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=42918
>
>
>
>
>
> --- Comment #1 from Robert Love<robert.w.love@intel.com> 2012-03-15 01:21:48 ---
> Fix was posted to linux-scsi here:
> http://www.spinics.net/lists/linux-scsi/msg58027.html
>
> Note that I Nacked my own patch but that others commented that the patch is
> correct. Please ignore the Nack; the patch is good.
>
> Can the submitted please verify that this fixes their issue?
>
I was unable to change the owner in the BZ. Bart, does this fix your
problem?
I've never worked with the kernel.org BZ, so I'm not sure if I need to
follow up on this anymore...
I'm not convinced that this needs to be rushed in for 3.3 since we're at
rc7. It's a warning in fcoe in point-to-multipoint mode and as much as
I'd like everything in fcoe working in every release I don't think this
will bother too many users.
Thanks, //Rob
next prev parent reply other threads:[~2012-03-15 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 12:16 [Bug 42918] New: fcoe: Enabling VN2VN mode triggers a circular locking complaint bugzilla-daemon
2012-03-14 1:22 ` [PATCH] fcoe: Drop the rtnl_mutex before calling fcoe_ctlr_link_up Robert Love
2012-03-15 1:21 ` [Bug 42918] fcoe: Enabling VN2VN mode triggers a circular locking complaint bugzilla-daemon
2012-03-15 1:28 ` Love, Robert W [this message]
2012-04-04 14:56 ` bugzilla-daemon
2012-04-04 15:21 ` bugzilla-daemon
2012-06-13 15:17 ` bugzilla-daemon
2012-06-13 15:17 ` bugzilla-daemon
2012-07-01 9:48 ` bugzilla-daemon
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=4F6145B1.30604@intel.com \
--to=robert.w.love@intel.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=bvanassche@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.