public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Joe Buehler <aspam@cox.net>
Cc: netdev@vger.kernel.org
Subject: Re: kernel panic in fib_rules_lookup [2.6.27.7 vendor-patched]
Date: Sat, 23 Oct 2010 17:11:09 +0200	[thread overview]
Message-ID: <1287846669.2658.247.camel@edumazet-laptop> (raw)
In-Reply-To: <1287805487.2658.5.camel@edumazet-laptop>

Le samedi 23 octobre 2010 à 05:44 +0200, Eric Dumazet a écrit :
> Le vendredi 22 octobre 2010 à 16:30 -0400, Joe Buehler a écrit :
> > Eric Dumazet wrote:
> > 
> > > Could you provide a disassembly of function fib_rules_lookup ?
> > 
> > Try looking in http://68.100.141.95:3000/linux-crash/.  There should be
> > the source file I am using (not current release if you recall), the .o,
> > the disassembly, and a -S compile that makes deducing the line numbers a
> > little easier.
> > 
> 
> Hmm, I'll take a look sometime in the future, thanks

Did that... Hmm...

I am wondering if smp_rcu_assign_pointer() (or more precisely smp_wmb())
is correctly implemented on octeon platform.

Try to add in fib_nl_newrule() right after the kzalloc bloc :

	rule = kzalloc(ops->rule_size, GFP_KERNEL);
	if (rule == NULL) {
		err = -ENOMEM;
		goto errout;
	}
+       rule->list.next = LIST_POISON1;
+       rule->list.prev = LIST_POISON2;


So that we can actually see if the NULL dereference bug you hit becomes
a "LIST_POISON1" dereference bug...




  reply	other threads:[~2010-10-23 15:11 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 [this message]
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"
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=1287846669.2658.247.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=aspam@cox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox