netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: netdev@oss.sgi.com
Subject: ip a flush problem on 2.6 kernels (fine on 2.4 kernels)
Date: Thu, 4 Mar 2004 03:08:15 +0100	[thread overview]
Message-ID: <200403040308.15880.arekm@pld-linux.org> (raw)

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've tried it on different 2.6 kernels (one from fedora, one from PLD) with 
different versions of iproute2 (usually latest). Friend tried it also with 
iproute2 from slackware - same result.

Same happens when using lo interface instead of ethX.

More description in RH bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116982

ps. doing that on Broadcom Corporation BCM4401 100Base-T ethX interface (using 
b44 driver) causes lock (but sysrq works) on 2.4.25 kernel. Would be nice if 
someone with that hardware could verify this.
-- 
Arkadiusz Miśkiewicz     CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

             reply	other threads:[~2004-03-04  2:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  2:08 Arkadiusz Miskiewicz [this message]
2004-03-04 13:13 ` ip a flush problem on 2.6 kernels (fine on 2.4 kernels) Andi Kleen
2004-03-10 19:37   ` Denis Vlasenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200403040308.15880.arekm@pld-linux.org \
    --to=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).