From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org, Liping Zhang <zlpnobody@gmail.com>
Subject: Re: [PATCH nf] netfilter: nf_tables: report error if stateful obj's name is truncated
Date: Thu, 19 Jan 2017 15:09:14 +0100 [thread overview]
Message-ID: <20170119140914.GA11241@salvia> (raw)
In-Reply-To: <1484834420-55121-1-git-send-email-zlpnobody@163.com>
On Thu, Jan 19, 2017 at 10:00:20PM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> Currently, if the user add a stateful object with the name size exceed
> NFT_OBJ_MAXNAMELEN - 1 (i.e. 31), we truncate it down to 31 silently.
> This is not friendly, furthermore, this will cause duplicated stateful
> objects when the first 31 characters of the name is same. So limit the
> stateful object's name size to NFT_OBJ_MAXNAMELEN - 1.
>
> After apply this patch, error message will be printed out like this:
> # name_32=$(printf "%0.sQ" {1..32})
> # nft add counter filter $name_32
> <cmdline>:1:1-52: Error: Could not process rule: Numerical result out
> of range
> add counter filter QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Good catch.
At quick glance, I can see other spots lacking this validation:
static const struct nla_policy nft_chain_policy[NFTA_CHAIN_MAX + 1] =
{
[NFTA_CHAIN_TABLE] = { .type = NLA_STRING },
Probably review and fix them in one go?
next prev parent reply other threads:[~2017-01-19 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 14:00 [PATCH nf] netfilter: nf_tables: report error if stateful obj's name is truncated Liping Zhang
2017-01-19 14:09 ` Pablo Neira Ayuso [this message]
2017-01-19 14:41 ` Liping Zhang
2017-01-19 15:22 ` Florian Westphal
2017-01-19 15:55 ` Patrick PIGNOL
2017-01-21 11:47 ` Patrick PIGNOL
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=20170119140914.GA11241@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@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).