From: Patrick McHardy <kaber@trash.net>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3 -next] netfilter: nft_ct: labels get support
Date: Tue, 18 Feb 2014 09:58:47 +0000 [thread overview]
Message-ID: <20140218095847.GA12178@macbook.localnet> (raw)
In-Reply-To: <1392715644-4458-1-git-send-email-fw@strlen.de>
On Tue, Feb 18, 2014 at 10:27:22AM +0100, Florian Westphal wrote:
> Takes advantage of the fact that the number of labels is currently
> restricted to 2**128, ie. the extension area will always fit into
> nft register.
>
> Patrick says the kernel registers need to be changed anyway to
> deal with concatentations so we will probably not run into issues
> when the number of labels increases in a future kernel release.
>
> +#ifdef CONFIG_NF_CONNTRACK_LABELS
> + case NFT_CT_LABELS: {
> + struct nf_conn_labels *labels = nf_ct_labels_find(ct);
> + unsigned int size;
> +
> + if (!labels)
> + goto err;
Is that really an error? I'd expect it to be equivalent with "no labels set",
which can also be matched on.
> + size = labels->words * sizeof(long);
> + if (size > sizeof(dest->data))
> + goto err;
Can't we check that during ->init() if the number is limited anyway?
> + memcpy(dest->data, labels->bits, size);
> +
> + if (size < sizeof(dest->data))
> + memset(((char *) dest->data) + size, 0,
> + sizeof(dest->data) - size);
> + return;
> + }
> +#endif
next prev parent reply other threads:[~2014-02-18 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 9:27 [PATCH 1/3 -next] netfilter: nft_ct: labels get support Florian Westphal
2014-02-18 9:27 ` [PATCH 2/3 libnftnl] expr: add conntrack label match support Florian Westphal
2014-02-18 9:27 ` [PATCH 3/3 nft] ct: connlabel matching support Florian Westphal
2014-02-18 10:09 ` Patrick McHardy
2014-02-18 9:58 ` Patrick McHardy [this message]
2014-02-18 10:13 ` [PATCH 1/3 -next] netfilter: nft_ct: labels get support Florian Westphal
2014-02-18 10:21 ` 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=20140218095847.GA12178@macbook.localnet \
--to=kaber@trash.net \
--cc=fw@strlen.de \
--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.