From: Samuel Ortiz <samuel@sortiz.org>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: irda rmmod lockdep trace.
Date: Sat, 10 Mar 2007 19:43:27 +0200 [thread overview]
Message-ID: <20070310174326.GA3816@sortiz.org> (raw)
In-Reply-To: <20070308225436.GA25184@redhat.com>
Hi Dave,
On Thu, Mar 08, 2007 at 05:54:36PM -0500, Dave Jones wrote:
> modprobe irda ; rmmod irda in 2.6.21rc3 gets me the spew below..
Well it seems that we call __irias_delete_object() from hashbin_delete(). Then
__irias_delete_object() calls itself hashbin_delete() again. We're trying to
get the lock recursively.
I'll try to fix that soon, thanks for the report.
Cheers,
Samuel.
> Dave
>
> NET: Registered protocol family 23
> NET: Unregistered protocol family 23
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.20-1.2966.fc7 #1
> ---------------------------------------------
> rmmod/16712 is trying to acquire lock:
> (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
>
> but task is already holding lock:
> (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
>
> other info that might help us debug this:
> 1 lock held by rmmod/16712:
> #0: (&hashbin->hb_spinlock){....}, at: [<ffffffff884bf476>] hashbin_delete+0x29/0x94 [irda]
>
> stack backtrace:
>
> Call Trace:
> [<ffffffff802a303b>] __lock_acquire+0x151/0xbc4
> [<ffffffff884c1517>] :irda:__irias_delete_attrib+0x0/0x31
> [<ffffffff802a3ea4>] lock_acquire+0x4c/0x65
> [<ffffffff884bf476>] :irda:hashbin_delete+0x29/0x94
> [<ffffffff80264011>] _spin_lock_irqsave+0x2c/0x3c
> [<ffffffff884bf476>] :irda:hashbin_delete+0x29/0x94
> [<ffffffff884c1918>] :irda:__irias_delete_object+0x0/0x39
> [<ffffffff884c193d>] :irda:__irias_delete_object+0x25/0x39
> [<ffffffff884bf48d>] :irda:hashbin_delete+0x40/0x94
> [<ffffffff884c5e3a>] :irda:iriap_cleanup+0x36/0x38
> [<ffffffff884c5fd6>] :irda:irda_cleanup+0x29/0x3a
> [<ffffffff802aa1e1>] sys_delete_module+0x199/0x1ca
> [<ffffffff8026ce36>] syscall_trace_enter+0x9a/0x9f
> [<ffffffff8025c2b5>] tracesys+0xdc/0xe1
>
>
> --
> http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-10 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 22:54 irda rmmod lockdep trace Dave Jones
2007-03-10 17:43 ` Samuel Ortiz [this message]
2007-03-12 0:38 ` Samuel Ortiz
2007-03-12 23:49 ` David Miller
2007-03-13 16:18 ` Samuel Ortiz
2007-03-14 0:50 ` Samuel Ortiz
2007-03-14 2:22 ` David Miller
2007-03-16 20:19 ` Samuel Ortiz
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=20070310174326.GA3816@sortiz.org \
--to=samuel@sortiz.org \
--cc=davej@redhat.com \
--cc=linux-kernel@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