From: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex•ru>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: netdev@vger•kernel.org
Subject: Re: Re: Kernel panic in fib_rules_lookup (kernel 2.6.32)
Date: Sun, 02 May 2010 14:46:26 +0400 [thread overview]
Message-ID: <382091272797186@web84.yandex.ru> (raw)
In-Reply-To: <1268154568.3113.19.camel@edumazet-laptop>
Hello,
09.03.10, 17:09, "Eric Dumazet" <eric.dumazet@gmail•com>:
> Le mardi 09 mars 2010 à 10:44 +0300, "Oleg A. Arkhangelsky" a écrit :
> > Hello,
> >
> > Got this kernel panic tomorrow. This PC is rather heavy loaded router with BGP full view (> 300K routes).
> > We're using FIB_TRIE. Last time we got similar panic about 1 month ago. Please, let me know if you
> > need additional information to debug (e.g. objdump). Thanks!
> >
> > Mar 9 10:08:55 bras-1 kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
> > Mar 9 10:08:55 bras-1 kernel: IP: [] fib_rules_lookup+0xa2/0xd0
> > Mar 9 10:08:55 bras-1 kernel: *pde = 00000000
> > Mar 9 10:08:55 bras-1 kernel: Thread overran stack, or stack corrupted
>
> Hmm...
Got the same panic, at the same place (fib_rules_lookup+0xa2/0xd0). Looks like the problem with NULL dereference is somewhere in list_for_each_entry_rcu macro. But I don't understand how this can be.
Any thoughts? :(
--
wbr, Oleg.
next prev parent reply other threads:[~2010-05-02 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:44 Kernel panic in fib_rules_lookup (kernel 2.6.32) "Oleg A. Arkhangelsky"
2010-03-09 17:09 ` Eric Dumazet
2010-05-02 10:46 ` "Oleg A. Arkhangelsky" [this message]
2010-05-02 16:31 ` Eric Dumazet
2010-05-02 17:14 ` "Oleg A. Arkhangelsky"
-- strict thread matches above, loose matches on Subject: below --
2010-03-09 17:21 "Oleg A. Arkhangelsky"
2010-03-09 18:22 ` Stephen Hemminger
2010-03-09 18:39 ` "Oleg A. Arkhangelsky"
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=382091272797186@web84.yandex.ru \
--to=sysoleg@yandex$(echo .)ru \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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