linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Florian Schmitt <florian@galois.de>
Cc: linux-kernel@vger.kernel.org, "David S. Miller" <davem@redhat.com>
Subject: Re: routing oddity in 2.5.59-mm8
Date: Sun, 9 Feb 2003 03:10:54 -0800	[thread overview]
Message-ID: <20030209031054.2b9ae2a2.akpm@digeo.com> (raw)
In-Reply-To: <200302091154.13187.florian@galois.de>

Florian Schmitt <florian@galois.de> wrote:
>
> in 2.5.59-mm8 the routing table behaves a bit strange:

me too:

vmm:/home/akpm# ip route show
192.168.2.0/24 dev eth0  scope link 
127.0.0.0/8 dev lo  scope link 
default via 192.168.2.1 dev eth0 
vmm:/home/akpm# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
vmm:/home/akpm# route del default
vmm:/home/akpm# route del default
SIOCDELRT: No such process

So `ip' can see the default route, but `route' cannot.

Reverting the spurious semicolon fix fixes it up.

diff -puN net/ipv4/fib_hash.c~a net/ipv4/fib_hash.c
--- 25/net/ipv4/fib_hash.c~a	2003-02-09 03:04:29.000000000 -0800
+++ 25-akpm/net/ipv4/fib_hash.c	2003-02-09 03:04:32.000000000 -0800
@@ -941,7 +941,7 @@ static __inline__ struct fib_node *fib_g
 
 			if (!iter->zone)
 				goto out;
-			if (iter->zone->fz_next)
+			if (iter->zone->fz_next);
 				break;
 		}
 		

_


      reply	other threads:[~2003-02-09 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 10:53 routing oddity in 2.5.59-mm8 Florian Schmitt
2003-02-09 11:10 ` Andrew Morton [this message]

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=20030209031054.2b9ae2a2.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=davem@redhat.com \
    --cc=florian@galois.de \
    --cc=linux-kernel@vger.kernel.org \
    /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).