From: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: kernel panic in fib_rules_lookup [2.6.27.7 vendor-patched]
Date: Sat, 23 Oct 2010 21:37:00 +0400 [thread overview]
Message-ID: <239681287855420@web159.yandex.ru> (raw)
In-Reply-To: <1287851745.2658.364.camel@edumazet-laptop>
23.10.2010, 20:36, "Eric Dumazet" <eric.dumazet@gmail.com>:
> With a normal workload, on a dual cpu machine, a missing memory barrier
> can stay un-noticed for quite a long time. The race window is so small
> that probability for the bug might be 0.0000001 % or something like
> that :(
Eric, I'd like to remind you that I've faced the similar problem on simple x86.
See http://kerneltrap.org/mailarchive/linux-netdev/2010/3/9/6271568
Two main differences for our case:
1) There is no userspace workload (except for bgpd), no changes in interfaces
2) We are not using multiple routing tables
This panic was pretty rare in our case (not more that 2 times per month).
Currently we're running fine with disabled CONFIG_IP_MULTIPLE_TABLES.
--
wbr, Oleg.
next prev parent reply other threads:[~2010-10-23 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 17:14 kernel panic in fib_rules_lookup [2.6.27.7 vendor-patched] Joe Buehler
2010-10-12 17:40 ` Eric Dumazet
2010-10-13 11:18 ` Joe Buehler
2010-10-20 17:43 ` Joe Buehler
2010-10-20 22:05 ` Eric Dumazet
2010-10-22 20:30 ` Joe Buehler
2010-10-23 3:44 ` Eric Dumazet
2010-10-23 15:11 ` Eric Dumazet
2010-10-23 15:24 ` Eric Dumazet
2010-10-23 15:40 ` Joe Buehler
2010-10-23 16:07 ` Eric Dumazet
2010-10-23 15:33 ` Joe Buehler
2010-10-23 16:35 ` Eric Dumazet
2010-10-23 17:37 ` "Oleg A. Arkhangelsky" [this message]
2010-10-23 19:44 ` Eric Dumazet
2010-10-26 18:43 ` David Miller
2010-10-26 13:29 ` Joe Buehler
2010-10-26 13:36 ` Eric Dumazet
2010-10-26 13:53 ` Joe Buehler
2010-10-26 13:58 ` Eric Dumazet
2010-10-26 14:33 ` Eric Dumazet
2010-10-26 14:41 ` Joe Buehler
2010-10-27 21:01 ` Joe Buehler
2010-10-27 21:05 ` Eric Dumazet
2010-12-02 13:36 ` Joe Buehler
2010-12-02 14:04 ` Eric Dumazet
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=239681287855420@web159.yandex.ru \
--to=sysoleg@yandex.ru \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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 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.