From: Pablo Neira Ayuso <pablo@gnumonks.org>
To: Florian Westphal <fw@strlen.de>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Patrick McHardy <kaber@trash.net>,
networking <netdev@vger.kernel.org>,
"Netfilter Development Maili..."
<netfilter-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: xt_nat_init: BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
Date: Thu, 13 Sep 2012 11:42:05 +0200 [thread overview]
Message-ID: <20120913094205.GA30612@1984> (raw)
In-Reply-To: <20120913093024.GL14750@breakpoint.cc>
On Thu, Sep 13, 2012 at 11:30:24AM +0200, Florian Westphal wrote:
> Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Hi Patrick,
> >
> > This happens in today's linux-next tree and is pretty reproducible.
> > [ 1.834544] nf_conntrack version 0.5.0 (1786 buckets, 7144 max)
> > [ 1.835406] ctnetlink v0.93: registering with nfnetlink.
> > [ 1.836202] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
> > [ 1.837539] IP: [<ffffffff81a19123>] mutex_lock_interruptible+0x23/0x70
>
> Should be fixed by
> commit 00545bec9412d130c77f72a08d6c8b6ad21d4a1e
> Author: Pablo Neira Ayuso <pablo@netfilter.org>
> Subject: netfilter: fix crash during boot if NAT has been compiled built-in
>
> But seems its not yet in net-next. Pablo?
I'll request the pull asap.
next prev parent reply other threads:[~2012-09-13 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 9:16 xt_nat_init: BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0 Fengguang Wu
2012-09-13 9:30 ` Florian Westphal
2012-09-13 9:42 ` Pablo Neira Ayuso [this message]
2012-09-13 9:33 ` Eric Dumazet
2012-09-13 10:55 ` Fengguang Wu
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=20120913094205.GA30612@1984 \
--to=pablo@gnumonks.org \
--cc=fengguang.wu@intel.com \
--cc=fw@strlen.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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.