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: nft_log: restrict the log prefix length to 127
Date: Tue, 24 Jan 2017 20:26:29 +0100 [thread overview]
Message-ID: <20170124192629.GA10120@salvia> (raw)
In-Reply-To: <1485094232-19683-1-git-send-email-zlpnobody@163.com>
On Sun, Jan 22, 2017 at 10:10:32PM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> First, log prefix will be truncated to NF_LOG_PREFIXLEN-1, i.e. 127,
> at nf_log_packet(), so the extra part is useless.
>
> Second, after adding a log rule with a very very long prefix, we will
> fail to dump the nft rules after this _special_ one, but acctually,
> they do exist. For example:
> # name_65000=$(printf "%0.sQ" {1..65000})
> # nft add rule filter output log prefix "$name_65000"
> # nft add rule filter output counter
> # nft add rule filter output counter
> # nft list chain filter output
> table ip filter {
> chain output {
> type filter hook output priority 0; policy accept;
> }
> }
>
> So now, restrict the log prefix length to NF_LOG_PREFIXLEN-1.
>
> Fixes: 96518518cc41 ("netfilter: add nftables")
> Signed-off-by: Liping Zhang <zlpnobody@gmail.com>
> ---
> I think this is different with http://patchwork.ozlabs.org/patch/717635/.
> So another separate patch will be better.
>
> include/uapi/linux/netfilter/nf_log.h | 2 ++
> net/netfilter/nf_log.c | 1 -
> net/netfilter/nft_log.c | 3 ++-
> 3 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/netfilter/nf_log.h b/include/uapi/linux/netfilter/nf_log.h
> index 8be21e0..d0b5fa9 100644
> --- a/include/uapi/linux/netfilter/nf_log.h
> +++ b/include/uapi/linux/netfilter/nf_log.h
> @@ -9,4 +9,6 @@
> #define NF_LOG_MACDECODE 0x20 /* Decode MAC header */
> #define NF_LOG_MASK 0x2f
>
> +#define NF_LOG_PREFIXLEN 128
Nitpick: xt_LOG allows 30 bytes, so we can probably stick to 32 bytes
here. Then, wait for usecases for larger strings, enlarging things is
easier than shrinking stuff later on (we can't actually, given that we
would break backward).
Probably we can keep __NF_LOG_PREFIXLEN 128 for what it already exists
in nf_log.c internally, and expose NF_LOG_PREFIXLEN of 32 bytes?
> #endif /* _NETFILTER_NF_LOG_H */
> diff --git a/net/netfilter/nf_log.c b/net/netfilter/nf_log.c
> index 3dca90d..ffb9e8a 100644
> --- a/net/netfilter/nf_log.c
> +++ b/net/netfilter/nf_log.c
> @@ -13,7 +13,6 @@
> /* Internal logging interface, which relies on the real
> LOG target modules */
>
> -#define NF_LOG_PREFIXLEN 128
> #define NFLOGGER_NAME_LEN 64
>
> static struct nf_logger __rcu *loggers[NFPROTO_NUMPROTO][NF_LOG_TYPE_MAX] __read_mostly;
> diff --git a/net/netfilter/nft_log.c b/net/netfilter/nft_log.c
> index 6271e40..6f6e644 100644
> --- a/net/netfilter/nft_log.c
> +++ b/net/netfilter/nft_log.c
> @@ -39,7 +39,8 @@ static void nft_log_eval(const struct nft_expr *expr,
>
> static const struct nla_policy nft_log_policy[NFTA_LOG_MAX + 1] = {
> [NFTA_LOG_GROUP] = { .type = NLA_U16 },
> - [NFTA_LOG_PREFIX] = { .type = NLA_STRING },
> + [NFTA_LOG_PREFIX] = { .type = NLA_STRING,
> + .len = NF_LOG_PREFIXLEN - 1 },
> [NFTA_LOG_SNAPLEN] = { .type = NLA_U32 },
> [NFTA_LOG_QTHRESHOLD] = { .type = NLA_U16 },
> [NFTA_LOG_LEVEL] = { .type = NLA_U32 },
> --
> 2.5.5
>
>
next prev parent reply other threads:[~2017-01-24 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 14:10 [PATCH nf] netfilter: nft_log: restrict the log prefix length to 127 Liping Zhang
2017-01-24 19:26 ` Pablo Neira Ayuso [this message]
2017-01-24 20:45 ` 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=20170124192629.GA10120@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).