From: Andi Kleen <ak@suse.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: linux-kernel@vger.kernel.org, kain@kain.org
Subject: Re: OOPS: Multipath routing 2.4.17
Date: 01 Mar 2002 23:43:49 +0100 [thread overview]
Message-ID: <p73sn7jkixm.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0203012316120.1420-100000@u.domain.uli.suse.lists.linux.kernel>
In-Reply-To: Julian Anastasov's message of "1 Mar 2002 23:30:20 +0100"
Julian Anastasov <ja@ssi.bg> writes:
> Hello,
>
> Kain wrote:
>
> > impossible 888
> > divide error: 0000
>
> > > > EIP; c024c5ea <fib_select_multipath+5a/a0> <=====
> > Trace; c02232e8 <ip_route_output_slow+318/670>
>
> There is no write locking in fib_select_multipath,
> combined with high rate of route resolutions and ... boom,
> fi->fib_power is 0:
In theory yes, but the
#if 1
if (power <= 0) {
printk(KERN_CRIT "impossible 777\n");
return;
}
#endif
should stop it; making it just not work, but not crash.
If he still gets a division by zero then something else is fishy.
-Andi
next parent reply other threads:[~2002-03-01 22:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0203012316120.1420-100000@u.domain.uli.suse.lists.linux.kernel>
2002-03-01 22:43 ` Andi Kleen [this message]
2002-03-02 1:01 ` OOPS: Multipath routing 2.4.17 Julian Anastasov
2002-03-01 23:05 ` Andi Kleen
2002-03-01 23:00 ` Andi Kleen
2002-03-02 1:20 ` Julian Anastasov
2002-03-02 0:27 Julian Anastasov
2002-03-02 0:25 ` Kain
2002-03-02 12:59 ` kuznet
2002-03-02 15:28 ` Julian Anastasov
2002-03-02 14:36 ` kuznet
2002-03-02 18:10 ` Julian Anastasov
[not found] <20020301173414.GA30037@kain.org.suse.lists.linux.kernel>
2002-03-01 18:12 ` Andi Kleen
2002-03-01 19:04 ` Kain
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 17:34 Kain
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=p73sn7jkixm.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=ja@ssi.bg \
--cc=kain@kain.org \
--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