From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: fenglg <flg2932946@163.com>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: kernel crash
Date: Tue, 29 Jan 2008 18:59:03 +0100 [thread overview]
Message-ID: <479F6967.2080808@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801291852070.14907@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jan 29 2008 18:32, fenglg wrote:
>> I use linux-2.6.18, and there is a bridge with eth0 and eth1. The eth0 and
>> eth1 connetcswitchs which use vlan trunk(802.1q). When i run system some
>> hours, the kernel is crash, anyone can help me.
>>
>> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010
>> EIP is at br_nf_pre_routing_finish+0x1d/0x340
>> eax: c16e7980 ebx: 00000000 ecx: 00000001 edx: c16e7980
>> esi: de4cb020 edi: c0456520 ebp: de8d2000 esp: c03fbce4
>> Code: 10 01 e9 7a ff ff ff 8d b4 26 00 00 00 00 55 57 56 53 81 ec c0 00 00 00 8b
>> 94 24 d4 00 00 00 8b 9a 80 00 00 00 8b 6a 14 8b 72 20 <8b> 43 10 a8 01 74 14 0f
>> b6 42 75 24 f8 0c 03 88 42 75 8b 43 10
>
> Thanks for the report.
>
> All signs point to skb->nf_bridge being NULL.
>
> static int br_nf_pre_routing_finish(struct sk_buff *skb)
> {
> struct net_device *dev = skb->dev;
> struct iphdr *iph = ip_hdr(skb);
> struct nf_bridge_info *nf_bridge = skb->nf_bridge;
> int err;
>
> boom-> if (nf_bridge->mask & BRNF_PKT_TYPE) {
>
>
> Hm... now what? :)
2.6.18 and 2.6.24 differ significantly in how the bridging stuff
is handled, so the preferred way would be to try to reproduce this
with 2.6.24. Debugging a 18 month old kernel doesn't seem too
useful unless we know the problem is still present.
next prev parent reply other threads:[~2008-01-29 17:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 10:32 kernel crash fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2012-05-30 17:35 Kernel crash Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
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=479F6967.2080808@trash.net \
--to=kaber@trash.net \
--cc=flg2932946@163.com \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@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.