From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
netfilter-devel@vger.kernel.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: NULL pointer dereference in xt_register_target()
Date: Wed, 5 Sep 2012 18:48:31 +0200 [thread overview]
Message-ID: <20120905164831.GA21836@1984> (raw)
In-Reply-To: <1346860506.13121.148.camel@edumazet-glaptop>
On Wed, Sep 05, 2012 at 05:55:06PM +0200, Eric Dumazet wrote:
> On Wed, 2012-09-05 at 23:43 +0800, Cong Wang wrote:
> > Hi, folks,
> >
> > The latest net-next tree can't boot due to a NULL ptr def
> > bug in the kernel, the full backtrack is:
> >
> > http://img1.douban.com/view/photo/photo/public/p1697139550.jpg
> >
> > the kernel .config file is:
> >
> > http://pastebin.com/9YTnkqKN
> >
> > I don't have time to look into the issue. If you need other info,
> > please let me know.
>
> It seems xt_nat_init() is called before xt_init(), so xt array is not
> yet setup.
I have enqueued the following patch to fix this:
http://1984.lsi.us.es/git/nf-next/commit/?id=00545bec9412d130c77f72a08d6c8b6ad21d4a1
e
commit 00545bec9412d130c77f72a08d6c8b6ad21d4a1e
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Wed Sep 5 18:24:55 2012 +0200
netfilter: fix crash during boot if NAT has been compiled built-in
Thanks.
next prev parent reply other threads:[~2012-09-05 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 15:43 NULL pointer dereference in xt_register_target() Cong Wang
2012-09-05 15:55 ` Eric Dumazet
2012-09-05 16:12 ` Eric Dumazet
2012-09-05 16:37 ` [PATCH net-next] netfilter: x_tables: xt_init() should run earlier Eric Dumazet
2012-09-05 16:53 ` Pablo Neira Ayuso
2012-09-05 16:59 ` Eric Dumazet
2012-09-08 17:50 ` Patrick McHardy
2012-09-08 19:50 ` Eric Dumazet
2012-09-05 16:48 ` Pablo Neira Ayuso [this message]
2012-09-06 14:27 ` NULL pointer dereference in xt_register_target() Cong Wang
2012-09-06 14:44 ` Pablo Neira Ayuso
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=20120905164831.GA21836@1984 \
--to=pablo@netfilter.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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).