From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: kaber@trash.net, exa.exa@gmail.com
Subject: Re: [PATCH nf] nf_tables: fix bogus warning in nft_data_uninit()
Date: Fri, 15 May 2015 22:08:46 +0200 [thread overview]
Message-ID: <20150515200846.GA3680@salvia> (raw)
In-Reply-To: <1431720355-3604-1-git-send-email-pablo@netfilter.org>
On Fri, May 15, 2015 at 10:05:55PM +0200, Pablo Neira Ayuso wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.orgi>
>
> From: Mirek Kratochvil <exa.exa@gmail.com>
Just for the record: I'll mangle this to restore your original
authorship before applying, that was my intention.
> The values 0x00000000-0xfffffeff are reserved for userspace datatype. When,
> deleting set elements with maps, a bogus warning is triggered.
>
> WARNING: CPU: 0 PID: 11133 at net/netfilter/nf_tables_api.c:4481 nft_data_uninit+0x35/0x40 [nf_tables]()
>
> This fixes the check accordingly to enum definition in
> include/linux/netfilter/nf_tables.h
prev parent reply other threads:[~2015-05-15 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 20:05 [PATCH nf] nf_tables: fix bogus warning in nft_data_uninit() Pablo Neira Ayuso
2015-05-15 20:08 ` Pablo Neira Ayuso [this message]
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=20150515200846.GA3680@salvia \
--to=pablo@netfilter.org \
--cc=exa.exa@gmail.com \
--cc=kaber@trash.net \
--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).