From: Patrick McHardy <kaber@trash.net>
To: "Oleg A. Arkhangelsky" <sysoleg@yandex.ru>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Kernel panic nf_nat_setup_info+0x5b3/0x6e0
Date: Wed, 02 Mar 2011 12:37:15 +0100 [thread overview]
Message-ID: <4D6E2BEB.50805@trash.net> (raw)
In-Reply-To: <118081298480841@web25.yandex.ru>
Am 23.02.2011 18:07, schrieb "Oleg A. Arkhangelsky":
> Hello,
>
> Got this panic yesterday:
> http://www.progtech.ru/~oleg/crash.txt
>
> The offending instruction is:
> cmpb 54(%edx), %cl # <variable>.tuple.dst.protonum,
>
> and here is the assembler code of net/ipv4/netfilter/nf_nat_core.c:
> http://www.progtech.ru/~oleg/nf_nat_core.s
>
> Quick investigation lead me to conclusion that the problem is in
> return of same_src function:
>
> return (t->dst.protonum == tuple->dst.protonum &&
> t->src.u3.ip == tuple->src.u3.ip &&
> t->src.u.all == tuple->src.u.all);
>
> So either t or tuple pointer is bad, but I don't understand how
> this can be.
I'm not sure myself, I'm guessing it has something to do with
reallocation of the NAT extension area. Please post your full
ruleset and any helpers in use.
> [2971152.752502] Pid: 0, comm: swapper Not tainted (2.6.32.25-pt #1)
Also please try whether the problem still happens with the current
kernel version.
next prev parent reply other threads:[~2011-03-02 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:07 Kernel panic nf_nat_setup_info+0x5b3/0x6e0 "Oleg A. Arkhangelsky"
2011-03-02 11:37 ` Patrick McHardy [this message]
2011-03-02 14:37 ` Changli Gao
2011-03-02 19:50 ` "Oleg A. Arkhangelsky"
2011-03-03 7:33 ` Changli Gao
2011-03-26 15:44 ` Changli Gao
2011-03-31 14:03 ` "Oleg A. Arkhangelsky"
2011-03-31 14:47 ` Eric Dumazet
2011-04-01 2:02 ` Changli Gao
2011-04-01 5:30 ` Eric Dumazet
2011-04-05 11:49 ` Patrick McHardy
2011-05-21 15:42 ` Changli Gao
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=4D6E2BEB.50805@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sysoleg@yandex.ru \
/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;
as well as URLs for NNTP newsgroup(s).