From: Kristof Provost <Kristof@provost-engineering.be>
To: netdev@vger.kernel.org
Subject: [BUG] IPv6 recursive locking
Date: Sun, 17 Feb 2008 14:12:29 +0000 [thread overview]
Message-ID: <20080217141229.GB1677@nereid> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm running the current git (1309d4e68497184d2fd87e892ddf14076c2bda98)
without problems. While I was toying with IPv6 on my local network I managed
to completely hang my machine whenever it receives or sends a neighbour
sollictation. At least, I think that's the cause. It started as soon as I
installed radvd on the router. The included trace seems to point in the same
direction.
The machine is a Dell Latitude D505 (so x86). Network interfaces are e100 and
ipw2200 (firmware not loaded). I'm currently using the e100.
I'll try to bisect it but here's the trace already. Let me know if
there's anything else you'd like to know.
[ 124.439831] =============================================
[ 124.443689] [ INFO: possible recursive locking detected ]
[ 124.443689] 2.6.25-rc2 #33
[ 124.443689] ---------------------------------------------
[ 124.443689] swapper/0 is trying to acquire lock:
[ 124.443689] (&n->lock){-+-+}, at: [<c0468d39>] neigh_resolve_output+0x139/0x290
[ 124.443689]
[ 124.443689] but task is already holding lock:
[ 124.443689] (&n->lock){-+-+}, at: [<c0468ea4>] neigh_timer_handler+0x14/0x280
[ 124.443689]
[ 124.443689] other info that might help us debug this:
[ 124.443689] 1 lock held by swapper/0:
[ 124.443689] #0: (&n->lock){-+-+}, at: [<c0468ea4>] neigh_timer_handler+0x14/0x280
[ 124.443689]
[ 124.443689] stack backtrace:
[ 124.443689] Pid: 0, comm: swapper Not tainted 2.6.25-rc2 #33
[ 124.443689] [<c014863a>] __lock_acquire+0xd3a/0xf40
[ 124.443689] [<c0137ec8>] __kernel_text_address+0x18/0x30
[ 124.443689] [<c01488a0>] lock_acquire+0x60/0x80
[ 124.443689] [<c0468d39>] neigh_resolve_output+0x139/0x290
[ 124.443689] [<c059287e>] _write_lock_bh+0x2e/0x40
[ 124.443689] [<c0468d39>] neigh_resolve_output+0x139/0x290
[ 124.443689] [<c0468d39>] neigh_resolve_output+0x139/0x290
[ 124.443689] [<c0148805>] __lock_acquire+0xf05/0xf40
[ 124.443689] [<c04e1650>] ndisc_dst_alloc+0xe0/0x170
[ 124.443689] [<c04d39f4>] ip6_output_finish+0xa4/0x110
[ 124.443689] [<c0147a1d>] __lock_acquire+0x11d/0xf40
[ 124.443689] [<c04d4759>] ip6_output+0x5b9/0xba0
[ 124.443689] [<c0456eb6>] sock_alloc_send_skb+0x176/0x1d0
[ 124.443689] [<c04e4eab>] __ndisc_send+0x33b/0x540
[ 124.443690] [<c04e4d6e>] __ndisc_send+0x1fe/0x540
[ 124.443690] [<c04e5b69>] ndisc_send_ns+0x69/0xa0
[ 124.443690] [<c04e6c8e>] ndisc_solicit+0xee/0x1b0
[ 124.443690] [<c01472b5>] mark_held_locks+0x35/0x80
[ 124.443690] [<c0592c65>] _spin_unlock_irqrestore+0x45/0x60
[ 124.443690] [<c01473f9>] trace_hardirqs_on+0x79/0x130
[ 124.443690] [<c012f99f>] __mod_timer+0x9f/0xb0
[ 124.443690] [<c0468fd3>] neigh_timer_handler+0x143/0x280
[ 124.443690] [<c012f2ca>] run_timer_softirq+0x14a/0x1c0
[ 124.443690] [<c0468e90>] neigh_timer_handler+0x0/0x280
[ 124.443690] [<c0468e90>] neigh_timer_handler+0x0/0x280
[ 124.443690] [<c012b4c4>] __do_softirq+0x84/0x100
[ 124.443690] [<c012b595>] do_softirq+0x55/0x60
[ 124.443690] [<c012b9e5>] irq_exit+0x65/0x80
[ 124.443690] [<c01073b0>] do_IRQ+0x40/0x70
[ 124.443690] [<c010585e>] common_interrupt+0x2e/0x34
[ 124.443690] [<c032007b>] acpi_power_on+0x3b/0x104
[ 124.443690] [<c0322af6>] acpi_idle_enter_simple+0x194/0x1fe
[ 124.443690] [<c0322727>] acpi_idle_enter_bm+0xc1/0x2fc
[ 124.443690] [<c03fff43>] cpuidle_idle_call+0x63/0xb0
[ 124.443690] [<c03ffee0>] cpuidle_idle_call+0x0/0xb0
[ 124.443690] [<c010380d>] cpu_idle+0x5d/0xf0
[ 124.443690] =======================
Kristof
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHuEDNUEZ9DhGwDugRAgHaAJ9L6i924sEqim1Ti+rZH2qmGESx6wCfWYIY
PI1kcoY3SWN/O9TOLgGQC20=
=cvKu
-----END PGP SIGNATURE-----
next reply other threads:[~2008-02-17 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 14:12 Kristof Provost [this message]
2008-02-17 18:30 ` [BUG] IPv6 recursive locking Daniel Lezcano
2008-02-17 20:37 ` Benjamin Thery
2008-02-18 2:43 ` David Miller
2008-02-18 2:41 ` David Miller
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=20080217141229.GB1677@nereid \
--to=kristof@provost-engineering.be \
--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