From: Luca <kornos.it@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: [2.6.18-rc4] lockdep warning at inet6_addr_add
Date: Fri, 11 Aug 2006 18:23:52 +0200 [thread overview]
Message-ID: <20060811162352.GA14795@dreamland.darkstar.lan> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF8, Size: 2249 bytes --]
Hi,
I get a warning from lockdep during boot; 2.6.18-rc3 don't have this
warning. I see a similar report in the archive (I haven't found time to
test the patch...):
http://marc.theaimsgroup.com/?l=linux-netdev&m=115506258902757&w=2
but my stacktrace is a bit different, so I'm reporting this one too:
=================================
[ INFO: inconsistent lock state ]
---------------------------------
inconsistent {in-softirq-W} -> {softirq-on-W} usage.
ifconfig/1812 [HC0[0]:SC0[0]:HE1:SE1] takes:
(&ifa->lock){-+..}, at: [<f1a0a4b9>] inet6_addr_add+0xd9/0x160 [ipv6]
{in-softirq-W} state was registered at:
[<b01342dd>] lock_acquire+0x5d/0x80
[<b030bafa>] _spin_lock_bh+0x3a/0x50
[<f1a0b76b>] addrconf_dad_timer+0x5b/0x100 [ipv6]
[<b0122bb9>] run_timer_softirq+0x149/0x170
[<b011ee62>] __do_softirq+0x62/0xc0
[<b011ef15>] do_softirq+0x55/0x60
[<b011f18b>] irq_exit+0x4b/0x50
[<b01059ec>] do_IRQ+0x4c/0x90
[<b0103c15>] common_interrupt+0x25/0x2c
[<b0101aa1>] cpu_idle+0x41/0x70
[<b0100537>] rest_init+0x37/0x40
[<b03fe7aa>] start_kernel+0x2ba/0x360
[<b0100199>] 0xb0100199
irq event stamp: 4501
hardirqs last enabled at (4501): [<b011f525>] local_bh_enable_ip+0x95/0x110
hardirqs last disabled at (4499): [<b011f4bf>] local_bh_enable_ip+0x2f/0x110
softirqs last enabled at (4500): [<f1a0729e>] ipv6_add_addr+0x3e/0x270 [ipv6]
softirqs last disabled at (4488): [<b030bc6e>] _read_lock_bh+0xe/0x50
other info that might help us debug this:
1 lock held by ifconfig/1812:
#0: (rtnl_mutex){--..}, at: [<b030a73c>] mutex_lock+0x1c/0x20
stack backtrace:
[<b0104312>] show_trace+0x12/0x20
[<b01048e9>] dump_stack+0x19/0x20
[<b01320de>] print_usage_bug+0x23e/0x250
[<b0132a39>] mark_lock+0x5a9/0x5c0
[<b0133a86>] __lock_acquire+0x806/0xd20
[<b01342dd>] lock_acquire+0x5d/0x80
[<b030baa5>] _spin_lock+0x35/0x50
[<f1a0a4b9>] inet6_addr_add+0xd9/0x160 [ipv6]
[<f1a0a7d9>] addrconf_add_ifaddr+0x69/0x80 [ipv6]
[<f1a02342>] inet6_ioctl+0x72/0x90 [ipv6]
[<b02aaa9e>] sock_ioctl+0xfe/0x1f0
[<b01720f8>] do_ioctl+0x28/0x80
[<b01721a7>] vfs_ioctl+0x57/0x2c0
[<b0172449>] sys_ioctl+0x39/0x60
[<b0103173>] syscall_call+0x7/0xb
Luca
--
Home: http://kronoz.cjb.net
Il tempo speso
a coltivare sogni
non è sprecato.
next reply other threads:[~2006-08-11 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 16:23 Luca [this message]
2006-08-12 3:14 ` Herbert Xu
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=20060811162352.GA14795@dreamland.darkstar.lan \
--to=kornos.it@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
all inboxes | Powered by JetHome®