Latest working kernel version: ? Earliest failing kernel version: 2.6.18-6 Distribution: Debian Hardware Environment: x86-686 Software Environment: stable release of Debian ETCH Problem Description: Ooops when adding a vlan on a device that is in slave mode of a bond device (Sory for my english :) Steps to reproduce: modprobe bonding mode=1 miimon=100 ifconfig eth0 promisc up ifenslave bond0 eth0 ifconfig bond0 up vconfig add eth0 2 => Ooops
Reply-To: akpm@linux-foundation.org (switching to email - please respond via emailed reply-to-all, not via the bugzilla web interface) On Wed, 19 Mar 2008 05:19:34 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=10283 > > Summary: Ooops when bonding and vlan on the same device > Product: Networking > Version: 2.5 > KernelVersion: 2.6.18 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: low > Priority: P1 > Component: Other > AssignedTo: acme@ghostprotocols.net > ReportedBy: amartins@crefidis.fr > > > Latest working kernel version: ? > Earliest failing kernel version: 2.6.18-6 > Distribution: Debian > Hardware Environment: x86-686 > Software Environment: stable release of Debian ETCH > Problem Description: > > Ooops when adding a vlan on a device that is in slave mode of a bond device > (Sory for my english :) > > Steps to reproduce: > > modprobe bonding mode=1 miimon=100 > ifconfig eth0 promisc up > ifenslave bond0 eth0 > ifconfig bond0 up > vconfig add eth0 2 => Ooops > Is a copy of the oops output available? Is there any possibility of testing a more up-to-date kernel? Thanks.
Andrew Morton <akpm@linux-foundation.org> wrote: [...] >On Wed, 19 Mar 2008 05:19:34 -0700 (PDT) >bugme-daemon@bugzilla.kernel.org wrote: > >> http://bugzilla.kernel.org/show_bug.cgi?id=10283 >> >> Summary: Ooops when bonding and vlan on the same device >> Product: Networking >> Version: 2.5 >> KernelVersion: 2.6.18 >> Platform: All >> OS/Version: Linux >> Tree: Mainline >> Status: NEW >> Severity: low >> Priority: P1 >> Component: Other >> AssignedTo: acme@ghostprotocols.net >> ReportedBy: amartins@crefidis.fr >> >> >> Latest working kernel version: ? >> Earliest failing kernel version: 2.6.18-6 >> Distribution: Debian >> Hardware Environment: x86-686 >> Software Environment: stable release of Debian ETCH >> Problem Description: >> >> Ooops when adding a vlan on a device that is in slave mode of a bond device >> (Sory for my english :) >> >> Steps to reproduce: >> >> modprobe bonding mode=1 miimon=100 >> ifconfig eth0 promisc up >> ifenslave bond0 eth0 >> ifconfig bond0 up >> vconfig add eth0 2 => Ooops >> > >Is a copy of the oops output available? > >Is there any possibility of testing a more up-to-date kernel? I don't see any errors when adding a VLAN approximately as described above when running 2.6.25-rc4. I say approximately because the steps must be performed in a different order than shown, but adding a VLAN to a slave that's up and promisc isn't generating an error for me. -J --- -Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
There is a copy of the Ooops. --------------------------------------------------------------------- Capricorne kernel: Oops: 0000 [#1] Capricorne kernel: SMP Capricorne kernel: CPU: 0 Capricorne kernel: EIP is at bond_netdev_event+0x51/0x74 [bonding] Capricorne kernel: eax: 00000000 ebx: ee2f22c8 ecx: c26fcc00 edx: 00000005 Capricorne kernel: esi: ee2e4fa0 edi: c26fcc00 ebp: 00000005 esp: d4b7bec0 Capricorne kernel: ds: 007b es: 007b ss: 0069 Capricorne kernel: Process vconfig (pid: 3025, ti=d4b7a000 task=c03ea000 task.ti=d4b7a000) Capricorne kernel: Stack: ee2f22c8 c0126287 c26fcc00 00000000 c038f66c c038f380 c0231b00 00000001 Capricorne kernel: 00000001 00000001 c26fcc00 c265c0de c26fccde c265c000 ee2fc634 0000000a Capricorne kernel: 00000000 30687465 00000000 00000000 00000000 00000000 00000000 0000000a Capricorne kernel: Call Trace: Capricorne kernel: Code: ee e8 a8 79 e5 d1 89 d8 e8 96 4c 00 00 89 d8 e8 12 56 00 00 b8 34 5a 2e ee e8 c3 79 e5 d1 eb 2a f6 c4 08 74 25 8b 41 70 83 fa 06 <8b> 98 68 01 00 00 74 07 83 fa 0b 75 12 eb 09 89 ca e8 cf fc ff Capricorne kernel: EIP: [<ee2d6760>] bond_netdev_event+0x51/0x74 [bonding] SS:ESP 0069:d4b7bec0 ------------------------------------------------------------------------------ I'm sory but i have no time to make more tests on more recent kernel (I only work with Debian ETCH stable kernel).
Sory missing the call Trace ------------------------------------------------------------------------ Capricorne kernel: Call Trace: Capricorne kernel: [<c0126287>] notifier_call_chain+0x19/0x32 Capricorne kernel: [<c0231b00>] register_netdevice+0x2c6/0x2d0 Capricorne kernel: [<ee2fc634>] vlan_ioctl_handler+0x347/0x53f [8021q] Capricorne kernel: [<c0229836>] sock_ioctl+0x13f/0x1b5 Capricorne kernel: [<c02296f7>] sock_ioctl+0x0/0x1b5 Capricorne kernel: [<c01686bc>] do_ioctl+0x1c/0x5d Capricorne kernel: [<c0168947>] vfs_ioctl+0x24a/0x25c Capricorne kernel: [<c022ad03>] sys_socketcall+0x51/0x181 Capricorne kernel: [<c01689a1>] sys_ioctl+0x48/0x5f Capricorne kernel: [<c0104883>] syscall_call+0x7/0xb ------------------------------------------------------------------------
Confirmed in 2.6.27-rc6 [root@the-village ~]# modprobe bonding mode=1 miimon=100 [root@the-village ~]# ifconfig eth0 promisc [root@the-village ~]# ifconfig bond0 up [root@the-village ~]# ifenslave bond0 eth0
Take that back -t ested wrong kernel