Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758001Ab0HQRSx (ORCPT ); Tue, 17 Aug 2010 13:18:53 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:57285 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753905Ab0HQRSu (ORCPT ); Tue, 17 Aug 2010 13:18:50 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=OIviyx3hKF6J9s1ASJxd6VwKob5UfjYPRZYPcub6aAnGp99I0FMO3rEVrtP67P59HC oWeBYIVZrMytFsVXx8yBYradSC0ctDQ03UNaWPeBC9e/aUUbgTeauQF6X/tt98v8nieD 7+sR1gx6HpgY7ImEydlUURsSfjfKmqqPqTr/4= Subject: Re: 2.6.36-rc1 ip6tables-resto: inconsistent lock state From: Eric Dumazet To: Ortwin =?ISO-8859-1?Q?Gl=FCck?= Cc: linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org In-Reply-To: <4C6AC2F8.90307@odi.ch> References: <4C6AC2F8.90307@odi.ch> Content-Type: text/plain; charset="UTF-8" Date: Tue, 17 Aug 2010 19:18:44 +0200 Message-ID: <1282065524.2448.117.camel@edumazet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3548 Lines: 91 Le mardi 17 août 2010 à 19:12 +0200, Ortwin Glück a écrit : > ================================= > [ INFO: inconsistent lock state ] > 2.6.36-rc1 #1 > --------------------------------- > inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. > ip6tables-resto/3098 [HC0[0]:SC0[0]:HE1:SE1] takes: > (&(&lock->lock)->rlock){+.?...}, at: [] get_counters+0xcc/0x160 > {IN-SOFTIRQ-W} state was registered at: > [] __lock_acquire+0x9b3/0x1850 > [] lock_acquire+0x64/0x80 > [] _raw_spin_lock+0x3d/0x50 > [] ip6t_do_table+0x5f/0x440 > [] ip6table_filter_hook+0x22/0x30 > [] nf_iterate+0x71/0x90 > [] nf_hook_slow+0xcf/0x120 > [] mld_sendpack+0x276/0x4d0 > [] mld_ifc_timer_expire+0x258/0x2f0 > [] run_timer_softirq+0x130/0x280 > [] __do_softirq+0x91/0x130 > [] do_softirq+0x5d/0x70 > [] irq_exit+0x75/0x80 > [] smp_apic_timer_interrupt+0x56/0x90 > [] apic_timer_interrupt+0x2f/0x34 > [] _raw_spin_lock+0x3d/0x50 > [] __d_lookup+0xca/0x160 > [] do_lookup+0x3d/0x1c0 > [] link_path_walk+0x3a6/0xa40 > [] path_walk+0x44/0xa0 > [] do_path_lookup+0x51/0x60 > [] user_path_at+0x3c/0x80 > [] sys_faccessat+0x9a/0x180 > [] sys_access+0x20/0x30 > [] syscall_call+0x7/0xb > irq event stamp: 5463 > hardirqs last enabled at (5463): [] local_bh_enable+0x62/0xe0 > hardirqs last disabled at (5461): [] local_bh_enable+0x24/0xe0 > softirqs last enabled at (5462): [] get_counters+0x7d/0x160 > softirqs last disabled at (5460): [] get_counters+0x26/0x160 > > other info that might help us debug this: > 2 locks held by ip6tables-resto/3098: > #0: (sk_lock-AF_INET6){+.+.+.}, at: [] ipv6_getsockopt+0x98/0xe0 > #1: (&xt[i].mutex){+.+.+.}, at: [] xt_find_table_lock+0x2c/0xe0 > > stack backtrace: > Pid: 3098, comm: ip6tables-resto Not tainted 2.6.36-rc1 #1 > Call Trace: > [] ? printk+0x18/0x1a > [] print_usage_bug+0x15c/0x1a0 > [] mark_lock+0x3a5/0x5b0 > [] ? check_usage_backwards+0x0/0xe0 > [] __lock_acquire+0x9f4/0x1850 > [] ? rb_insert_color+0xd3/0x110 > [] ? __kmalloc+0x6f/0xf0 > [] lock_acquire+0x64/0x80 > [] ? get_counters+0xcc/0x160 > [] _raw_spin_lock+0x3d/0x50 > [] ? get_counters+0xcc/0x160 > [] get_counters+0xcc/0x160 > [] do_ip6t_get_ctl+0x1ad/0x2d0 > [] ? mutex_lock_interruptible_nested+0x23a/0x3c0 > [] nf_sockopt+0x105/0x180 > [] ? local_bh_enable+0x4a/0xe0 > [] nf_getsockopt+0x24/0x30 > [] ipv6_getsockopt+0xb3/0xe0 > [] rawv6_getsockopt+0x3b/0x170 > [] ? might_fault+0x5a/0xb0 > [] sock_common_getsockopt+0x22/0x30 > [] sys_getsockopt+0x4c/0xa0 > [] sys_socketcall+0xfc/0x270 > [] sysenter_do_call+0x12/0x36 > > > Full log attached. Yes, this is the fourth time it is reported here ;) http://marc.info/?l=linux-kernel&m=128199018321130&w=2 Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/