Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751546AbWIBUjb (ORCPT ); Sat, 2 Sep 2006 16:39:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751545AbWIBUjb (ORCPT ); Sat, 2 Sep 2006 16:39:31 -0400 Received: from khc.piap.pl ([195.187.100.11]:32915 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S1751539AbWIBUja (ORCPT ); Sat, 2 Sep 2006 16:39:30 -0400 To: Cc: netdev@vger.kernel.org Subject: 2.6.18-rc5 with GRE, iptables and Speedtouch ADSL, PPP over ATM From: Krzysztof Halasa Date: Sat, 02 Sep 2006 22:39:28 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4230 Lines: 113 Hi, FYI: Just enabled kernel lock testers on my old laptop machine doing "internet services". 2.6.18-rc5, i686. All details available on request, of course. There is IP GRE tunnel here running over ADSL connection (USB Thomson/Alcatel Speedtouch 330, PPP over ATM, in-kernel drivers). Ethernet is DLink Tulip-based (PC Card 32-bit), probably not relevant here. Iptables doing mostly ACCEPTs, REJECT and DROPs in INPUT and FORWARD, there is also MASQUERADE but it probably doesn't matter. Few ip rules directing some traffic to the GRE tunnel as well. ======================================================= [ INFO: possible circular locking dependency detected ] ------------------------------------------------------- swapper/0 is trying to acquire lock: (&dev->queue_lock){-+..}, at: [] dev_queue_xmit+0x56/0x290 but task is already holding lock: (&dev->_xmit_lock){-+..}, at: [] dev_queue_xmit+0x224/0x290 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&dev->_xmit_lock){-+..}: [] lock_acquire+0x76/0xa0 [] _spin_lock_bh+0x31/0x40 [] dev_activate+0x69/0x120 [] dev_open+0x59/0x70 [] dev_change_flags+0x51/0x110 [] devinet_ioctl+0x484/0x670 [] inet_ioctl+0x6b/0x80 [] sock_ioctl+0x118/0x200 [] do_ioctl+0x20/0x70 [] vfs_ioctl+0x57/0x290 [] sys_ioctl+0x39/0x60 [] sysenter_past_esp+0x56/0x8d -> #0 (&dev->queue_lock){-+..}: [] lock_acquire+0x76/0xa0 [] _spin_lock+0x2c/0x40 [] dev_queue_xmit+0x56/0x290 [] ip_output+0x1ad/0x250 [] ipgre_tunnel_xmit+0x412/0x740 [ip_gre] [] dev_hard_start_xmit+0x1bb/0x220 [] dev_queue_xmit+0x23b/0x290 [] ip_output+0x1ad/0x250 [] reject+0x37c/0x6d0 [] ipt_do_table+0x2b8/0x330 [] ipt_hook+0x27/0x30 [] nf_iterate+0x59/0x80 [] nf_hook_slow+0x4a/0xc0 [] ip_local_deliver+0x175/0x1c0 [] ip_rcv+0x25c/0x480 [] netif_receive_skb+0x15e/0x1e0 [] process_backlog+0x82/0x110 [] net_rx_action+0x72/0x120 [] __do_softirq+0x55/0xc0 [] do_softirq+0x63/0xd0 other info that might help us debug this: 2 locks held by swapper/0: #0: (&table->lock){-.-+}, at: [] ipt_do_table+0x51/0x330 #1: (&dev->_xmit_lock){-+..}, at: [] dev_queue_xmit+0x224/0x290 stack backtrace: [] show_trace+0x12/0x20 [] dump_stack+0x19/0x20 [] print_circular_bug_tail+0x61/0x70 [] __lock_acquire+0xac6/0xd70 [] lock_acquire+0x76/0xa0 [] _spin_lock+0x2c/0x40 [] dev_queue_xmit+0x56/0x290 [] ip_output+0x1ad/0x250 [] ipgre_tunnel_xmit+0x412/0x740 [ip_gre] [] dev_hard_start_xmit+0x1bb/0x220 [] dev_queue_xmit+0x23b/0x290 [] ip_output+0x1ad/0x250 [] reject+0x37c/0x6d0 [] ipt_do_table+0x2b8/0x330 [] ipt_hook+0x27/0x30 [] nf_iterate+0x59/0x80 [] nf_hook_slow+0x4a/0xc0 [] ip_local_deliver+0x175/0x1c0 [] ip_rcv+0x25c/0x480 [] netif_receive_skb+0x15e/0x1e0 [] process_backlog+0x82/0x110 [] net_rx_action+0x72/0x120 [] __do_softirq+0x55/0xc0 [] do_softirq+0x63/0xd0 ======================= [] irq_exit+0x35/0x40 [] do_IRQ+0x8f/0xf0 [] common_interrupt+0x25/0x2c [] cpu_idle+0x39/0x50 [] rest_init+0x1e/0x30 [] start_kernel+0x25e/0x2c0 [] 0xc0100199 -- Krzysztof Halasa -- VGER BF report: U 0.5 - 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/