All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: ip a flush problem on 2.6 kernels (fine on 2.4 kernels)
Date: Thu, 4 Mar 2004 14:13:19 +0100	[thread overview]
Message-ID: <20040304141319.2d1cb112.ak@suse.de> (raw)
In-Reply-To: <200403040308.15880.arekm@pld-linux.org>

On Thu, 4 Mar 2004 03:08:15 +0100
Arkadiusz Miskiewicz <arekm@pld-linux.org> wrote:

> 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.

-Andi

diff -u iproute2/ip/ipaddress.c~ iproute2/ip/ipaddress.c
--- iproute2/ip/ipaddress.c~	2004-03-07 20:54:52.000000000 +0100
+++ iproute2/ip/ipaddress.c	2004-03-07 21:02:12.000000000 +0100
@@ -623,6 +623,9 @@
 				fflush(stdout);
 				return 0;
 			}
+#if 1
+			break; 
+#else
 			round++;
 			if (flush_update() < 0)
 				exit(1);
@@ -630,6 +633,7 @@
 				printf("\n*** Round %d, deleting %d addresses ***\n", round, filter.flushed);
 				fflush(stdout);
 			}
+#endif
 		}
 	}
 

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  2:08 ip a flush problem on 2.6 kernels (fine on 2.4 kernels) Arkadiusz Miskiewicz
2004-03-04 13:13 ` Andi Kleen [this message]
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=20040304141319.2d1cb112.ak@suse.de \
    --to=ak@suse.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.