From: Florian Westphal <fw@strlen.de>
To: Anatole Denis <natolumin@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: nft_set_hash: fix fast_ops for 2-len keys
Date: Sat, 28 Oct 2017 13:33:04 +0200 [thread overview]
Message-ID: <20171028113304.GA7663@breakpoint.cc> (raw)
In-Reply-To: <1509187202.2986.0@smtp.gmail.com>
Anatole Denis <natolumin@gmail.com> wrote:
> I'm not very familiar with this part of the code, so it's very possible I
> don't know what I'm talking about, but there is also nft_hash_deactivate
> which is doing a jhash over the key and will still incorrectly hash 2-byte
> keys.
Oh right, thanks for pointing this out. I will send a v2.
prev parent reply other threads:[~2017-10-28 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 10:57 [PATCH nf-next] netfilter: nft_set_hash: fix fast_ops for 2-len keys Florian Westphal
2017-10-28 10:40 ` Anatole Denis
2017-10-28 11:33 ` Florian Westphal [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=20171028113304.GA7663@breakpoint.cc \
--to=fw@strlen.de \
--cc=natolumin@gmail.com \
--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.