From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Robert Love <robert.w.love@intel.com>
Cc: linux-scsi@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH 4/6] fcoe: Don't hold rtnl_mutex in fcoe_update_src_mac
Date: Thu, 10 May 2012 08:53:15 +0100 [thread overview]
Message-ID: <1336636395.5323.7.camel@dabdike> (raw)
In-Reply-To: <20120420191643.4634.91026.stgit@localhost6.localdomain6>
On Fri, 2012-04-20 at 12:16 -0700, Robert Love wrote:
> The rtnl_mutex was held to protect calls to dev_uc_add
> and dev_uc_del. Holding rtnl is not required as those
> functions make use of the netif_addr_lock* API to
> protect the MAC changing.
>
> This change fixes the following regression by removing
> the rtnl usage when fcoe_update_src_mac is called.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=42918
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (&fip->ctlr_mutex){+.+...}:
> [<c1091f70>] lock_acquire+0x80/0x1b0
> [<c147655d>] mutex_lock_nested+0x6d/0x340
> [<f8970c32>] fcoe_ctlr_link_up+0x22/0x180 [libfcoe]
> [<f894620e>] fcoe_create+0x47e/0x6e0 [fcoe]
> [<f8973dd3>] fcoe_transport_create+0x143/0x250 [libfcoe]
> [<c10527e0>] param_attr_store+0x30/0x60
> [<c1052696>] module_attr_store+0x26/0x40
> [<c11a201e>] sysfs_write_file+0xae/0x100
> [<c11449df>] vfs_write+0x8f/0x160
> [<c1144cbd>] sys_write+0x3d/0x70
> [<c147a0c4>] syscall_call+0x7/0xb
>
> -> #0 (rtnl_mutex){+.+.+.}:
> [<c109164b>] __lock_acquire+0x140b/0x1720
> [<c1091f70>] lock_acquire+0x80/0x1b0
> [<c147655d>] mutex_lock_nested+0x6d/0x340
> [<c13a10c4>] rtnl_lock+0x14/0x20
> [<f89445ac>] fcoe_update_src_mac+0x2c/0xb0 [fcoe]
> [<f8971712>] fcoe_ctlr_timer_work+0x712/0xb60 [libfcoe]
> [<c104fb69>] process_one_work+0x179/0x5d0
> [<c10502f1>] worker_thread+0x121/0x2d0
> [<c10550ed>] kthread+0x7d/0x90
> [<c1481a82>] kernel_thread_helper+0x6/0x10
>
> other info that might help us debug this:
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&fip->ctlr_mutex);
> lock(rtnl_mutex);
> lock(&fip->ctlr_mutex);
> lock(rtnl_mutex);
>
> *** DEADLOCK ***
>
> Signed-off-by: Robert Love <robert.w.love@intel.com>
> Nacked-by: Robert Love <robert.w.love@intel.com>
Nacked-by? I'm assuming, since you signed off above, that you're
actually happy with the patch, and I just removed this line as some
accidental addition.
James
next prev parent reply other threads:[~2012-05-10 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:16 [PATCH 0/6] libfc, libfcoe and fcoe patches for scsi-misc Robert Love
2012-04-20 19:16 ` [PATCH 1/6] fcoe: remove lport from net device before doing per cpu rx thread cleanup Robert Love
2012-04-20 19:16 ` [PATCH 2/6] libfc: flush lport worker after its disabled Robert Love
2012-04-20 19:16 ` [PATCH 3/6] libfc: defer releasing master lport until complete fcoe interface cleanuped up Robert Love
2012-04-20 19:16 ` [PATCH 4/6] fcoe: Don't hold rtnl_mutex in fcoe_update_src_mac Robert Love
2012-05-10 7:53 ` James Bottomley [this message]
2012-04-20 19:16 ` [PATCH 5/6] libfcoe: fix VN2VN N_Port_ID Beacon source MAC Robert Love
2012-04-20 19:16 ` [PATCH 6/6] fcoe: remove a stray unlock Robert Love
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=1336636395.5323.7.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.com \
/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).