From: "Jason A. Donenfeld" Subject: Re: [PATCH v2 3/4] secure_seq: use siphash24 instead of md5_transform Date: Wed, 14 Dec 2016 18:49:26 +0100 Message-ID: References: <20161214035927.30004-1-Jason@zx2c4.com> <20161214035927.30004-3-Jason@zx2c4.com> <1e502c6b-cda3-c46d-2535-fcfb58f443a9@stressinduktion.org> <063D6719AE5E284EB5DD2968C1650D6DB023F7BD@AcuExch.aculab.com> Reply-To: kernel-hardening@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Hannes Frederic Sowa , Netdev , "kernel-hardening@lists.openwall.com" , Andi Kleen , LKML , Linux Crypto Mailing List To: David Laight Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB023F7BD@AcuExch.aculab.com> List-Id: linux-crypto.vger.kernel.org On Wed, Dec 14, 2016 at 3:47 PM, David Laight wrote: > Just remove the __packed and ensure that the structure is 'nice'. > This includes ensuring there is no 'tail padding'. > In some cases you'll need to put the port number into a 32bit field. I'd rather not. There's no point in wasting extra cycles on hashing useless data, just for some particular syntactic improvement. __packed __aligned(8) will do what we want perfectly, I think. > I'd also require that the key be aligned. Yep, I'll certainly do this for the siphash24_aligned version in the v3.