From: Nikolay Aleksandrov <nikolay@redhat.com>
To: netfilter-devel@vger.kernel.org
Cc: pablo@netfilter.org, kaber@trash.net,
Nikolay Aleksandrov <nikolay@redhat.com>
Subject: Re: [PATCH v2] netfilter: nf_tables: check if payload offset is a power of 2
Date: Sun, 16 Feb 2014 13:33:58 +0100 [thread overview]
Message-ID: <5300B036.9010108@redhat.com> (raw)
In-Reply-To: <1392553338-1978-1-git-send-email-nikolay@redhat.com>
On 02/16/2014 01:22 PM, Nikolay Aleksandrov wrote:
> Add a check if payload's offset is a power of 2 when selecting ops.
> The fast ops were meant for well aligned offsets, also this fixes a
> small bug when using unaligned offset and length of 3 which causes
> only 1 byte to be loaded because the fast ops are chosen.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
> ---
> v2: use is_power_of_2, and adjust order of checks as per Patrick's comment
>
> Sorry for the noise, I shouldn't hurry so much. This patch applies to
> Dave's -net tree.
>
> net/netfilter/nft_payload.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nft_payload.c b/net/netfilter/nft_payload.c
> index a2aeb31..3321ce0 100644
> --- a/net/netfilter/nft_payload.c
> +++ b/net/netfilter/nft_payload.c
> @@ -135,7 +135,8 @@ nft_payload_select_ops(const struct nft_ctx *ctx,
> if (len == 0 || len > FIELD_SIZEOF(struct nft_data, data))
> return ERR_PTR(-EINVAL);
>
> - if (len <= 4 && IS_ALIGNED(offset, len) && base != NFT_PAYLOAD_LL_HEADER)
> + if (len <= 4 && is_power_of_2(offset) && IS_ALIGNED(offset, len) &&
> + base != NFT_PAYLOAD_LL_HEADER)
> return &nft_payload_fast_ops;
> else
> return &nft_payload_ops;
>
Self-NAK as per our discussion in v1, there'll be v3 with the check for
length alignment.
prev parent reply other threads:[~2014-02-16 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 12:22 [PATCH v2] netfilter: nf_tables: check if payload offset is a power of 2 Nikolay Aleksandrov
2014-02-16 12:33 ` Nikolay Aleksandrov [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=5300B036.9010108@redhat.com \
--to=nikolay@redhat.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).