From: Patrick McHardy <kaber@trash.net>
To: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
Cc: Netdev <netdev@vger.kernel.org>, Pablo <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org
Subject: Re: nft 0.4, crash on list
Date: Sun, 22 Mar 2015 05:33:13 +0000 [thread overview]
Message-ID: <20150322053313.GA16931@acer.localdomain> (raw)
In-Reply-To: <a457f2eac526c6fe6e6f80634358d587@visp.net.lb>
On 22.03, Denys Fedoryshchenko wrote:
> Sorry for noise, seems git version working fine!
Still this shouldn't be happening. Just to confirm, you were using an
unpatched kernel and by git you mean nftables git?
> On 2015-03-22 00:49, Denys Fedoryshchenko wrote:
> >Additionally, if i will do "nft flush table mangle" , with this table
> >added i will get this:
> >[ 42.800078] ------------[ cut here ]------------
> >[ 42.800092] WARNING: CPU: 3 PID: 2868 at
> >net/netfilter/nf_tables_api.c:4122 nft_data_uninit+0x35/0x50
> >[nf_tables]()
next prev parent reply other threads:[~2015-03-22 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 22:32 nft 0.4, crash on list Denys Fedoryshchenko
2015-03-21 22:49 ` Denys Fedoryshchenko
2015-03-21 23:40 ` Denys Fedoryshchenko
2015-03-22 5:33 ` Patrick McHardy [this message]
2015-03-22 8:05 ` Denys Fedoryshchenko
2015-03-22 19:29 ` Pablo Neira Ayuso
2015-03-22 19:29 ` 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=20150322053313.GA16931@acer.localdomain \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nuclearcat@nuclearcat.com \
--cc=pablo@netfilter.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