[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHmME9pCjBiZr9n9g4On2GACbDm52vt1SkDXBz4yTVzaKF0ZWQ@mail.gmail.com>
Date: Thu, 15 Dec 2016 22:16:23 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>, David Laight <David.Laight@...lab.com>,
Netdev <netdev@...r.kernel.org>,
Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>, LKML <linux-kernel@...r.kernel.org>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>, "Daniel J . Bernstein" <djb@...yp.to>,
Eric Biggers <ebiggers3@...il.com>
Subject: Re: Re: [PATCH v2 1/4] siphash: add
cryptographically secure hashtable function
On Thu, Dec 15, 2016 at 10:14 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> I think you can/should just use the natural alignment for "u64".
>
> For architectures that need 8-byte alignment, u64 will already be
> properly aligned. For architectures (like x86-32) that only need
> 4-byte alignment, you get it.
I should have added mention of that with my previous email. For the
parameters that are always a multiple of u64 -- namely, the key -- I
now do that in v5 of the patchset. So this is already done.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
