netdev - Re: Re: Kernel panic in fib_rules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 02 May 2010 18:31:04 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	"\"Oleg A. Arkhangelsky\"" <sysoleg@...dex.ru>
Cc:	netdev@...r.kernel.org
Subject: Re: Re: Kernel panic in fib_rules_lookup (kernel 2.6.32)

Le dimanche 02 mai 2010 à 14:46 +0400, "Oleg A. Arkhangelsky" a écrit :
> Hello,
> 
> 09.03.10, 17:09, "Eric Dumazet" <eric.dumazet@...il.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? :(
> 

Do you have any modify rules activity ?

I dont understand why we need synchronize_rcu() in fib_nl_delrule() but
this certainly not a bug.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html