From: "David S. Miller" <davem@davemloft.net>
To: Martin Lucina <mato@kotelna.sk>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: OOPS in Linux 2.6.9, fib_release_info
Date: Tue, 30 Nov 2004 20:46:44 -0800 [thread overview]
Message-ID: <20041130204644.4319f974.davem@davemloft.net> (raw)
In-Reply-To: <20041201011612.GA3423@kotelna.sk>
On Wed, 1 Dec 2004 02:16:12 +0100
Martin Lucina <mato@kotelna.sk> wrote:
> I have found a reproducible OOPS in fib_release_info, in the 2.6.9 kernel.
> Tested on two different systems, one UP, one SMP, both i386, both w/
> CONFIG_PREEMPT=y, both Debian sarge, both w/ iproute2 version 20010824-13.1
> (Debian).
Already fixed in 2.6.10 by this patch.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/10/25 20:09:20-07:00 ehrhardt@mathematik.uni-ulm.de
# [IPV4]: Do not try to unhash null-netdev nexthops.
#
# Signed-off-by: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
# net/ipv4/fib_semantics.c
# 2004/10/25 20:09:01-07:00 ehrhardt@mathematik.uni-ulm.de +2 -0
# [IPV4]: Do not try to unhash null-netdev nexthops.
#
# Signed-off-by: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
diff -Nru a/net/ipv4/fib_semantics.c b/net/ipv4/fib_semantics.c
--- a/net/ipv4/fib_semantics.c 2004-11-30 20:22:10 -08:00
+++ b/net/ipv4/fib_semantics.c 2004-11-30 20:22:10 -08:00
@@ -163,6 +163,8 @@
if (fi->fib_prefsrc)
hlist_del(&fi->fib_lhash);
change_nexthops(fi) {
+ if (!nh->nh_dev)
+ continue;
hlist_del(&nh->nh_hash);
} endfor_nexthops(fi)
fi->fib_dead = 1;
prev parent reply other threads:[~2004-12-01 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 1:16 Martin Lucina
2004-12-01 4:46 ` David S. Miller [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=20041130204644.4319f974.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mato@kotelna.sk \
--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
all inboxes | Powered by JetHome®