From: Patrick McHardy <kaber@trash.net>
To: "Christoph A." <casmls@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nftables: NULL pointer dereference
Date: Thu, 23 Jul 2009 14:26:14 +0200 [thread overview]
Message-ID: <4A6856E6.9030600@trash.net> (raw)
Christoph A. wrote:
> when executing the testscript [1] (just to see if my nftables setup is
> working), I get the following stack trace.
>
> [1] http://article.gmane.org/gmane.linux.network/122512
>
> I'm using the latest version from:
> git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nft-2.6.git
> kernel config is attached
>
> BUG: unable to handle kernel NULL pointer dereference at 00000014
> IP: [<f8b471ff>] nft_validate_data_load+0x20/0x53 [nf_tables]
Thanks for the report. This is likely happening because the kernel
includes support for some changes for which I haven't pushed out the
corresponding userspace support yet, but it certainly shouldn't oops.
I'll look into it ...
next reply other threads:[~2009-07-23 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 12:26 Patrick McHardy [this message]
2009-07-23 15:03 ` nftables: NULL pointer dereference Patrick McHardy
2009-07-23 23:48 ` Christoph A.
-- strict thread matches above, loose matches on Subject: below --
2009-07-19 22:12 Christoph A.
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=4A6856E6.9030600@trash.net \
--to=kaber@trash.net \
--cc=casmls@gmail.com \
--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.