From: Ingo Molnar <mingo@elte.hu>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: "Linux-Kernel," <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
NetDEV list <netdev@vger.kernel.org>
Subject: [patch, -rc5-mm1] lock validator: special locking: net/ipv4/igmp.c #2
Date: Thu, 1 Jun 2006 08:35:37 +0200 [thread overview]
Message-ID: <20060601063537.GA19931@elte.hu> (raw)
In-Reply-To: <4807377b0605311704g44fe10f1oc54315276890071@mail.gmail.com>
* Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:
> well, when running e1000 through some code paths on FC4 +
> 2.6.17-rc5-mm1 + ingo's latest rollup patch, with this lockdep debug
> option enabled I got this:
>
> e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
>
> ======================================
> [ BUG: bad unlock ordering detected! ]
> --------------------------------------
> mDNSResponder/2361 is trying to release lock (&in_dev->mc_list_lock) at:
> [<ffffffff81233f5a>] ip_mc_add_src+0x85/0x1f8
ok, could you try the patch below? (i also updated the rollup with this
fix)
Ingo
---------------------
Subject: lock validator: special locking: net/ipv4/igmp.c #2
From: Ingo Molnar <mingo@elte.hu>
another case of non-nested unlocking igmp.c.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
net/ipv4/igmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/net/ipv4/igmp.c
===================================================================
--- linux.orig/net/ipv4/igmp.c
+++ linux/net/ipv4/igmp.c
@@ -1646,7 +1646,7 @@ static int ip_mc_add_src(struct in_devic
return -ESRCH;
}
spin_lock_bh(&pmc->lock);
- read_unlock(&in_dev->mc_list_lock);
+ read_unlock_non_nested(&in_dev->mc_list_lock);
#ifdef CONFIG_IP_MULTICAST
sf_markstate(pmc);
next prev parent reply other threads:[~2006-06-01 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 0:04 2.6.17-rc5-mm1 lockdep output Jesse Brandeburg
2006-06-01 6:34 ` Arjan van de Ven
2006-06-01 6:35 ` Ingo Molnar [this message]
2006-06-02 6:47 ` [patch, -rc5-mm1] lock validator: special locking: net/ipv4/igmp.c #2 Jesse Brandeburg
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=20060601063537.GA19931@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).