On Thursday 04 March 2004 15:13, Andi Kleen wrote:
On Thu, 4 Mar 2004 03:08:15 +0100
Arkadiusz Miskiewicz [off-list ref] wrote:
quoted
The problem is that
ip a a 192.168.0.1/24 dev eth0
ip link set eth0 down
ip a flush dev eth0
Here on my vanilla 2.6.2 it locks eating CPU - it does netlink
communication over and over. This ,,hang'' doesn't happen when
interface is in UP state. Also doesn't happen on 2.4 kernels.
I fixed it with this patch for iproute2 here. It's not clear to me at
all how it ever worked before. The loop seems to be just wrong.
Does iproute2 have a homepage again? Where?
--
vda