From: Florian Westphal <fw@strlen.de>
To: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Fwd: Re: [BUG] Fatal exception in interrupt - nf_nat_cleanup_conntrack during IPv6 tests
Date: Wed, 10 Apr 2013 11:04:36 +0200 [thread overview]
Message-ID: <20130410090436.GG3013@breakpoint.cc> (raw)
----- Forwarded message -----
Subject: Re: [BUG] Fatal exception in interrupt - nf_nat_cleanup_conntrack during IPv6 tests
CAI Qian <caiqian@redhat.com> wrote:
[ CC'd nf-devel ]
> Just hit this very often during IPv6 tests in both the latest stable
> and mainline kernel.
>
> [ 3597.206166] Modules linked in:
[..]
> nf_nat_ipv4(F-)
[..]
> [ 3597.804861] RIP: 0010:[<ffffffffa03227f2>] [<ffffffffa03227f2>] nf_nat_cleanup_conntrack+0x42/0x70 [nf_nat]
> [ 3597.855207] RSP: 0018:ffff880202c63d40 EFLAGS: 00010246
> [ 3597.881350] RAX: 0000000000000000 RBX: ffff8801ac7bec28 RCX: ffff8801d0eedbe0
> [ 3597.917226] RDX: dead000000200200 RSI: 0000000000000011 RDI: ffffffffa03265b8
[..]
> [ 3598.421036] <IRQ>
> [ 3598.430467] [<ffffffffa0305bb4>] __nf_ct_ext_destroy+0x44/0x60 [nf_conntrack]
> [ 3598.499191] [<ffffffffa02fd3fe>] nf_conntrack_free+0x2e/0x70 [nf_conntrack]
> [ 3598.534121] [<ffffffffa02febed>] destroy_conntrack+0xbd/0x110 [nf_conntrack]
> [ 3598.569981] [<ffffffff81532187>] nf_conntrack_destroy+0x17/0x20
> [ 3598.599579] [<ffffffffa02fe77c>] death_by_timeout+0xdc/0x1b0 [nf_conntrack]
[..]
> [ 3599.241868] Code: 83 ec 08 0f b6 58 11 84 db 74 43 48 01 c3 48 83 7b 20 00 74 39 48 c7 c7 b8 65 32 a0 e8 98 fc 2e e1 48 8b 03 48 8b 53 08 48 85 c0 <48> 89 02 74 04 48 89 50 08 48 ba 00 02 20 00 00 00 ad de 48 c7
> [ 3599.337037] RIP [<ffffffffa03227f2>] nf_nat_cleanup_conntrack+0x42/0x70 [nf_nat]
Looks like we tried to remove bysource hash twice (rdx is
LIST_POISON_2).
I wonder if this would explain it:
static void nf_nat_l4proto_clean(u8 l3proto, u8 l4proto)
{
[..]
/* Step 1 - remove from bysource hash */
clean.hash = true;
for_each_net(net)
nf_ct_iterate_cleanup(net, nf_nat_proto_clean, &clean);
A nfct->timer fires and a conntrack is free'd before step 2 memsets the
nat extension. In that case, we would try to delete nat->bysource
again?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
----- End forwarded message -----
next reply other threads:[~2013-04-10 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 9:04 Florian Westphal [this message]
2013-04-10 9:23 ` Fwd: Re: [BUG] Fatal exception in interrupt - nf_nat_cleanup_conntrack during IPv6 tests Patrick McHardy
2013-04-10 9:32 ` Florian Westphal
2013-04-10 9:41 ` Patrick McHardy
2013-04-10 14:56 ` Florian Westphal
2013-04-10 14:57 ` Patrick McHardy
2013-04-11 9:34 ` Florian Westphal
2013-04-11 10:40 ` Patrick McHardy
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=20130410090436.GG3013@breakpoint.cc \
--to=fw@strlen.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 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).