From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.17-mm4 + hostap + pcmcia + lockdep -- possible recursive locking detected -- (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69
Date: Sat, 1 Jul 2006 18:04:30 -0700 [thread overview]
Message-ID: <a44ae5cd0607011804i2326c350ta6262feec1e6805e@mail.gmail.com> (raw)
I have patches for hostap, pcmcia and lockdep applied to this kernel.
These patches are the ones resulting from several recent message
threads.
I just noticed this in my kernel log:
[ INFO: possible recursive locking detected ]
---------------------------------------------
multiload-apple/2820 is trying to acquire lock:
(af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>]
sock_def_readable+0x15/0x69
but task is already holding lock:
(af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>]
sock_def_readable+0x15/0x69
other info that might help us debug this:
3 locks held by multiload-apple/2820:
#0: (rtnl_mutex){--..}, at: [<c120028e>] mutex_lock+0x1c/0x1f
#1: (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>]
sock_def_readable+0x15/0x69
#2: (&priv->lock){.+..}, at: [<f90472c9>]
ipw_irq_tasklet+0x54/0x10c1 [ipw2200]
stack backtrace:
[<c1003502>] show_trace_log_lvl+0x54/0xfd
[<c1003b6a>] show_trace+0xd/0x10
[<c1003c0e>] dump_stack+0x19/0x1b
[<c102ccd6>] __lock_acquire+0x755/0x970
[<c102d1b6>] lock_acquire+0x60/0x80
[<c1201533>] _read_lock+0x23/0x32
[<c119d8db>] sock_def_readable+0x15/0x69
[<c11b5621>] netlink_broadcast+0x1c6/0x2b8
[<c11ad712>] wireless_send_event+0x28a/0x29c
[<f9047d02>] ipw_irq_tasklet+0xa8d/0x10c1 [ipw2200]
[<c101a4e7>] tasklet_action+0x45/0x76
[<c101a709>] __do_softirq+0x55/0xb0
[<c1004a64>] do_softirq+0x58/0xbd
[<c101a6a8>] irq_exit+0x3f/0x4b
[<c1004b89>] do_IRQ+0xc0/0xcf
[<c1002fd9>] common_interrupt+0x25/0x2c
next reply other threads:[~2006-07-02 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 1:04 Miles Lane [this message]
2006-07-02 13:29 ` Ingo Molnar
2006-07-02 13:34 ` Ingo Molnar
2006-07-03 6:08 ` Miles Lane
2006-07-03 6:10 ` Ingo Molnar
2006-07-05 7:56 ` Miles Lane
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=a44ae5cd0607011804i2326c350ta6262feec1e6805e@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®