[Bridge] Re: a problem about brctl

[Bridge] Re: a problem about brctl

[Stephen Hemminger]

Haisen.Zhang wrote:

>shemminger，
>
>    I have a problem with brctl application,following is my operations:
>	
>	vconfig add eth0 3
>
>	brctl addbr  br0
>	
>	brctl addbr  br1
>
>	brctl addif br0 eth0.3
>	
>	brctl delif br0 eth0.3
>
>	brctl addif br1 eth0.3
>
>　  brctl delif br0 eth0.3
>
>	brctl delif br0 eth0.3
>
>	At lastest operation,I delif eth0.3 from br0 several times,and the system will crack down, and the following infomation will display at console:
># brctl delif br0 eth0.3
>zhsdebug:  main() line 60....
><4>zhs_debug:br_ioctl_deviceless_stub() line 314 
><4>br_ioctl_deviceless() start,arg0=0x00000000,arg1=0...
><4>zhs_debug:br_ioctl_deviceless_stub() line 316 
><4>zhs_debug:br_ioctl_deviceless_stub() line 314 
><4>br_ioctl_deviceless() start,arg0=0x7fff7d68,arg1=32...
><4>zhs_debug:br_ioctl_deviceless() line 266 
><4>zhs_debug:br_get_bridge_ifindices() line 270 
><4>zhs_debug:br_get_bridge_ifindices() line 280 
><4>br_get_bridge_ifindices() return 2....
><4>br_ioctl_deviceless() get arg1=2...
><4>toUser:0D 00 00 00  0A 00 00 00                           ........
><4>zhs_debug:br_ioctl_deviceless() line 275 
><4>zhs_debug:br_ioctl_deviceless_stub() line 316 
>Oops in fault.c:do_page_fault, line 204:
>$0 : 00000000 1000fc00 000002d0 000000b4 9566e000 941e3d34 95aae8c0 00000000
>$8 : 00000000 00000000 955f3832 00000000 9422954a fffffff9 955f37ea ffffffff
>$16: 941e3d34 941e3cec 95bc5800 955f39b0 00000007 7fff7930 95bc5800 004563b0
>$24: 0000000a 00000002                   955f2000 955f3928 7fff78b0 94181d38
>Hi : 00000000
>Lo : 00000000
>epc  : 94181d50    Not tainted
>Status: 1000fc03
>Cause : 10800008
>Process brctl (pid: 345, stackpage=955f2000)
>Stack: 941e3cec 941e3d34 00000121 00000000 955f39b0 7fff7d2f 95bc5800 7fff7930
>       941826dc 941824c4 941e3fec 941e4008 00000039 00000000 0e000080 ff44aa0a
>       0e000080 ff44aa0a 00000000 00000258 000000c8 00000190 00000258 000000c8
>       00000190 00000000 00007530 00000190 00000000 00000000 00000000 00000000
>       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>       00000000 ...
>Call Trace: [<941e3cec>] [<941e3d34>] [<941826dc>] [<941824c4>] [<941e3fec>] [<941e4008>]
> [<94035220>] [<9402dae8>] [<941e4004>] [<941e4100>] [<941e3fec>] [<941e4100>]
> [<941e3fec>] [<94182f74>] [<94182f38>] [<941e3fec>] [<941e4100>] [<94180288>]
> [<940d7f08>] [<940df9c8>] [<940dd608>] [<94073d4c>] [<940dfce4>] [<94074d34>]
> [<9412f9b0>] [<9405ce84>] [<940d5c70>] [<9406cd68>] [<9406cd74>] [<9405b7d0>]
> [<9402dae8>]
>
>Code: 8cc2000c  8cc30008  00021080 <8c64003c> 00531021  ac440000  8cc60000  54c0fff9  8cc2000c 
>Segmentation fault
>			
>
>	why? can you help me?
>	Thank you very much.
> 				
>
>　　　　　　　　Haisen.Zhang
>　　　　　　　　zhs@cybertan.com.cn
>　　　　　　　　　　2006-01-05
>  
>
Which kernel version are you using? A bug like that existed in earlier 2.4
versions.