[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5547C7F0.5010905@intel.com>
Date: Mon, 04 May 2015 12:26:40 -0700
From: Tadeusz Struk <tadeusz.struk@...el.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: David Howells <dhowells@...hat.com>, corbet@....net,
keescook@...omium.org, qat-linux@...el.com, jwboyer@...hat.com,
richard@....at, linux-kernel@...r.kernel.org, steved@...hat.com,
vgoyal@...hat.com, james.l.morris@...cle.com, jkosina@...e.cz,
zohar@...ux.vnet.ibm.com, davem@...emloft.net,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH RFC 1/2] crypto: add PKE API
On 05/02/2015 05:07 PM, Herbert Xu wrote:
>>>> > >> #define CRYPTO_ALG_TYPE_AHASH 0x0000000a
>>>>> > >> > +#define CRYPTO_ALG_TYPE_PKE 0x0000000b
>>>>> > >> > #define CRYPTO_ALG_TYPE_RNG 0x0000000c
>>> > > Will filling a hole cause a problem with something that got obsoleted?
>> >
>> > I hope not. I checked as far back as 2.6.18 and I don't see any clash.
>> > Herbert, what do you think?
> Indeed you can't use this hole as it'll make you a hash algorithm.
So in this case isn't RNG a hash algorithm as well?
Anyway will something like this be ok with you:
diff --git a/include/linux/crypto.h b/include/linux/crypto.h
index ee14140..ac18cd3 100644
--- a/include/linux/crypto.h
+++ b/include/linux/crypto.h
@@ -41,7 +41,7 @@
/*
* Algorithm masks and types.
*/
-#define CRYPTO_ALG_TYPE_MASK 0x0000000f
+#define CRYPTO_ALG_TYPE_MASK 0xf000000f
#define CRYPTO_ALG_TYPE_CIPHER 0x00000001
#define CRYPTO_ALG_TYPE_COMPRESS 0x00000002
#define CRYPTO_ALG_TYPE_AEAD 0x00000003
@@ -54,6 +54,7 @@
#define CRYPTO_ALG_TYPE_AHASH 0x0000000a
#define CRYPTO_ALG_TYPE_RNG 0x0000000c
#define CRYPTO_ALG_TYPE_PCOMPRESS 0x0000000f
+#define CRYPTO_ALG_TYPE_PKE 0x10000001
#define CRYPTO_ALG_TYPE_HASH_MASK 0x0000000e
#define CRYPTO_ALG_TYPE_AHASH_MASK 0x0000000c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists