From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [Bugme-new] [Bug 9920] New: kernel panic when using ebtables redirect target Date: Fri, 8 Feb 2008 17:59:42 -0800 Message-ID: <20080208175942.a8b495ac.akpm@kernel.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: bugme-daemon@bugzilla.kernel.org, mingching.tiew@redtone.com To: netdev@vger.kernel.org Return-path: Received: from hera.kernel.org ([140.211.167.34]:32964 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756360AbYBICCj (ORCPT ); Fri, 8 Feb 2008 21:02:39 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 8 Feb 2008 17:40:20 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=9920 > > Summary: kernel panic when using ebtables redirect target > Product: Networking > Version: 2.5 > KernelVersion: 2.6.24 and 2.6.24-git > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Other > AssignedTo: acme@ghostprotocols.net > ReportedBy: mingching.tiew@redtone.com > > > Latest working kernel version: 2.6.22 ( did not test 2.6.23 ) > Earliest failing kernel version: 2.6.24 > Distribution: > Hardware Environment: > Software Environment: bridge working as a router > Problem Description: when using ebtables to set up target-redirect, there will > be kernel panic > > Steps to reproduce: > 1. set up a basic bridge br0 with slaves eth0, eth1 > 2. on the bridge setup a default router to route traffic > 3. use ebtables to setup target redirect, > > ebtables -t broute -A BROUTING --logical-in br0 \ > -p ipv4 --ip-protocol tcp --ip-destination-port 80 \ > -j redirect --redirect-target ACCEPT > > 4. from a client which is connect to the bridge, > send some traffic to allow the BROUTE chain to be > traversed :- > > lynx http://www.google.com > > 5. Kernel panic :- > > Pid: 0, comm: swapper Not tainted (2.6.24-tmc #1) > EIP: 0060:[] EFLAGS: 00000217 CPU: 0 > EIP is at ebt_do_table+0x4ea/0x5d0 [ebtables] > EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000001 > ESI: c69f1178 EDI: c69f1108 EBP: c69f1000 ESP: c0315e20 > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > Process swapper (pid: 0, ti=c0314000 task=c02f1300 task.ti=c0314000) > Stack: 00000000 c69f11dc 00000004 00000000 c28c7800 c2b79c20 00000005 c69de350 > 00000001 00000002 c69ed040 c69ed040 00000000 00000000 c69f1000 000000b0 > 000000b0 c29b0812 00000000 c69f1122 00000000 00000000 0000a0c3 c29b0812 > Call Trace: > [] ebt_broute+0x22/0x30 [ebtable_broute] > [] br_handle_frame+0xb8/0x220 [bridge] > [] netif_receive_skb+0x19c/0x440 > [] process_backlog+0x6b/0xd0 > [] net_rx_action+0x105/0x1b0 > [] __do_softirq+0x75/0xf0 > [] do_softirq+0x37/0x40 > [] irq_exit+0x75/0x80 > [] smp_apic_timer_interrupt+0x57/0x90 > [] apic_timer_interrupt+0x28/0x30 > [] default_idle+0x0/0x40 > [] default_idle+0x2f/0x40 > [] cpu_idle+0x73/0xa0 > [] start_kernel+0x2c5/0x340 > [] unknown_bootoption+0x0/0x1e0 > ======================= > Code: 00 00 83 f9 fe 74 64 83 f9 fc 0f 84 d7 fb ff ff 83 f9 fd 0f 84 bb fc ff > ff 8b 5c 24 30 8b 54 24 34 8d 04 5b 8d 04 82 8b 54 24 20 <89> 28 42 89 50 08 8b > 5f 6c 01 df 89 78 04 8b 6c 24 38 8b 54 24 > EIP: [] ebt_do_table+0x4ea/0x5d0 [ebtables] SS:ESP 0068:c0315e20 > >