kernel-hardening - Re: [PATCH v3 1/3] siphash: add cryptographically secure hashtable function

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHmME9rgGnAYTDaPSo=7mZj=jinka0+QTYA8TBb9WXY9S1QmRg@mail.gmail.com>
Date: Wed, 14 Dec 2016 22:21:50 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, Netdev <netdev@...r.kernel.org>, 
	kernel-hardening@...ts.openwall.com, LKML <linux-kernel@...r.kernel.org>, 
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>, 
	Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>, "Daniel J . Bernstein" <djb@...yp.to>, 
	Linus Torvalds <torvalds@...ux-foundation.org>, Eric Biggers <ebiggers3@...il.com>, 
	David Laight <David.Laight@...lab.com>
Subject: Re: [PATCH v3 1/3] siphash: add cryptographically secure hashtable function

Interesting. Evidently gcc 4.8 doesn't like my use of:

enum siphash_lengths {
       SIPHASH24_KEY_LEN = 16,
       SIPHASH24_ALIGNMENT = 8
};

I'll convert this to the more boring:

#define SIPHASH24_KEY_LEN 16
#define SIPHASH24_ALIGNMENT 8

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.