linux-kernel - 2.6.23-rc1-mm2 + cpufreq patch -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 2 Aug 2007 19:53:32 -0700
From:	"Miles Lane" <miles.lane@...il.com>
To:	"Andrew Morton" <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Jeff Garzik" <jgarzik@...ox.com>
Subject: 2.6.23-rc1-mm2 + cpufreq patch -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.

I am running Ubuntu Gutsy with latest updates.
When I run "/etc/init.d/networking stop" with my custom kernel, I get:

=================================
[ INFO: inconsistent lock state ]
2.6.23-rc1-mm2 #21
---------------------------------
inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
ifconfig/8982 [HC0[0]:SC0[0]:HE1:SE1] takes:
 (&tp->lock){++..}, at: [<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
{in-hardirq-W} state was registered at:
  [<c0144837>] __lock_acquire+0x430/0xbca
  [<c0145047>] lock_acquire+0x76/0x9d
  [<c031ffe0>] _spin_lock+0x23/0x32
  [<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
  [<c0154b44>] handle_IRQ_event+0x1a/0x4f
  [<c0155c6c>] handle_fasteoi_irq+0x7d/0xb6
  [<c0109a5a>] do_IRQ+0xaf/0xd9
  [<ffffffff>] 0xffffffff
irq event stamp: 1501
hardirqs last  enabled at (1501): [<c0173232>] kfree+0xc7/0xdb
hardirqs last disabled at (1500): [<c01731d2>] kfree+0x67/0xdb
softirqs last  enabled at (1480): [<c02cf082>] dev_deactivate+0x87/0xa0
softirqs last disabled at (1478): [<c031fffa>] _spin_lock_bh+0xb/0x37

other info that might help us debug this:
1 lock held by ifconfig/8982:
 #0:  (rtnl_mutex){--..}, at: [<c031ed95>] mutex_lock+0x1c/0x1f

stack backtrace:
 [<c01080ab>] show_trace_log_lvl+0x12/0x25
 [<c0108a9e>] show_trace+0xd/0x10
 [<c0108bac>] dump_stack+0x16/0x18
 [<c0143374>] print_usage_bug+0x107/0x114
 [<c0143bdd>] mark_lock+0x1e9/0x400
 [<c01448ab>] __lock_acquire+0x4a4/0xbca
 [<c0145047>] lock_acquire+0x76/0x9d
 [<c031ffe0>] _spin_lock+0x23/0x32
 [<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
 [<c015506f>] free_irq+0xc9/0xf2
 [<f8b9ef56>] rtl8139_close+0xac/0x14a [8139too]
 [<c02c2135>] dev_close+0x4e/0x6b
 [<c02c128a>] dev_change_flags+0x9f/0x152
 [<c03015f2>] devinet_ioctl+0x209/0x506
 [<c0301f5a>] inet_ioctl+0x86/0xa4
 [<c02b8211>] sock_ioctl+0x1a9/0x1c7
 [<c017ffca>] do_ioctl+0x22/0x67
 [<c0180258>] vfs_ioctl+0x249/0x25c
 [<c0180297>] sys_ioctl+0x2c/0x45
 [<c0106f02>] sysenter_past_esp+0x6b/0xb5
 =======================
eth2: link down
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/