netdev - Re: problems with ib-bonding of 2.6.24-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <472EFB28.9090000@gmail.com>
Date:	Mon, 05 Nov 2007 13:14:48 +0200
From:	Moni Shoua <monisonlists@...il.com>
To:	Moni Shoua <monis@...taire.com>
CC:	Jay Vosburgh <fubar@...ibm.com>, netdev@...r.kernel.org
Subject: Re: problems with ib-bonding of 2.6.24-rc1

Moni Shoua wrote:
> Basically, what I see is that after a while commands like ifconfig or ip stucks.
> I only use sysfs  to configure bonding (which also stucks after a while).
> 

Maybe some extra information might help

This is what happens in the kernel while the command 'ip' is stucked in user level.

bond0         S ffffffff8057eb80     0  4799      2
 ffff8100060e7ee0 0000000000000046 0000000000000000 0000000000000286
 ffff810004259820 ffff81000160d760 ffff810004259a28 0000000200000019
 00000000ffffffff ffffffff80244f94 0000000000000000 0000000000000000
Call Trace:
 [<ffffffff80244f94>] queue_delayed_work_on+0xaf/0xbe
 [<ffffffff880597c7>] :bonding:bond_mii_monitor+0x0/0x9a
 [<ffffffff80244fe8>] worker_thread+0x0/0xe4
 [<ffffffff80245089>] worker_thread+0xa1/0xe4
 [<ffffffff8024833b>] autoremove_wake_function+0x0/0x2e
 [<ffffffff80248213>] kthread+0x47/0x74
 [<ffffffff8020c458>] child_rip+0xa/0x12
 [<ffffffff802481cc>] kthread+0x0/0x74
 [<ffffffff8020c44e>] child_rip+0x0/0x12

ip            D ffffffff8057eb80     0  4842   4841
 ffff81000615bb88 0000000000000082 0000000000000000 ffffffff80289b5c
 ffff810006123140 ffff8100016a77e0 ffff810006123348 00000003045c45a8
 00000000ffffffff 0000000000000000 0000000000000000 0000000000000000
Call Trace:
 [<ffffffff80289b5c>] __link_path_walk+0xb97/0xcec
 [<ffffffff80563a64>] __mutex_lock_slowpath+0x68/0xa3
 [<ffffffff805638f6>] mutex_lock+0x1a/0x1e
 [<ffffffff804ecffb>] rtnetlink_rcv+0x9/0x1e
 [<ffffffff804f30e6>] netlink_unicast+0x1c3/0x236
 [<ffffffff804f3a69>] netlink_sendmsg+0x296/0x2a9
 [<ffffffff80266235>] zone_statistics+0x3f/0x60
 [<ffffffff804d9806>] sock_sendmsg+0xcb/0xe3
 [<ffffffff8024833b>] autoremove_wake_function+0x0/0x2e
 [<ffffffff80267960>] __do_fault+0x35e/0x398
 [<ffffffff804d8d09>] move_addr_to_kernel+0x25/0x36
 [<ffffffff804d9bd0>] sys_sendto+0x128/0x151
 [<ffffffff804da686>] sys_getsockname+0x72/0xa2
 [<ffffffff8020b63e>] system_call+0x7e/0x83


I also attach my .config

View attachment "dot-config" of type "text/plain" (38409 bytes)