linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v2 01/15] crypto: Add a flag to identify crypto instances
Date: Wed, 17 Aug 2011 14:09:36 +0200	[thread overview]
Message-ID: <20110817120936.GY16877@secunet.com> (raw)
In-Reply-To: <20110817120859.GX16877@secunet.com>

The upcomming crypto user configuration api needs to identify
crypto instances. This patch adds a flag that is set if the
algorithm is an instance that is build from templates.

Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
 crypto/algapi.c        |    1 +
 include/linux/crypto.h |    5 +++++
 2 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/crypto/algapi.c b/crypto/algapi.c
index c3cf1a6..6fd9bcf 100644
--- a/crypto/algapi.c
+++ b/crypto/algapi.c
@@ -493,6 +493,7 @@ int crypto_register_instance(struct crypto_template *tmpl,
 		goto err;
 
 	inst->alg.cra_module = tmpl->module;
+	inst->alg.cra_flags |= CRYPTO_ALG_INSTANCE;
 
 	down_write(&crypto_alg_sem);
 
diff --git a/include/linux/crypto.h b/include/linux/crypto.h
index e5e468e..cba4d63 100644
--- a/include/linux/crypto.h
+++ b/include/linux/crypto.h
@@ -72,6 +72,11 @@
 #define CRYPTO_ALG_TESTED		0x00000400
 
 /*
+ * Set if the algorithm is an instance that is build from telplates.
+ */
+#define CRYPTO_ALG_INSTANCE		0x00000800
+
+/*
  * Transform masks and values (for crt_flags).
  */
 #define CRYPTO_TFM_REQ_MASK		0x000fff00
-- 
1.7.0.4

  reply	other threads:[~2011-08-17 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 12:08 [PATCH v2 00/15] crypto user configuration api Steffen Klassert
2011-08-17 12:09 ` Steffen Klassert [this message]
2011-08-17 12:10 ` [PATCH v2 02/15] crypto: Add userspace configuration API Steffen Klassert
2011-08-22  6:59   ` Herbert Xu
2011-08-29  8:18     ` Steffen Klassert
2011-09-02  3:50       ` Herbert Xu
2011-08-17 12:10 ` [PATCH v2 03/15] crypto: Add a report function pointer to crypto_type Steffen Klassert
2011-08-17 12:11 ` [PATCH v2 04/15] crypto: Add userspace report for larval type algorithms Steffen Klassert
2011-08-17 12:12 ` [PATCH v2 05/15] crypto: Add userspace report for shash " Steffen Klassert
2011-08-17 12:12 ` [PATCH v2 06/15] crypto: Add userspace report for ahash " Steffen Klassert
2011-08-17 12:13 ` [PATCH v2 07/15] crypto: Add userspace report for blkcipher " Steffen Klassert
2011-08-17 12:13 ` [PATCH v2 08/15] crypto: Add userspace report for ablkcipher " Steffen Klassert
2011-08-17 12:14 ` [PATCH v2 09/15] crypto: Add userspace report for givcipher " Steffen Klassert
2011-08-17 12:15 ` [PATCH v2 10/15] crypto: Add userspace report for aead " Steffen Klassert
2011-08-17 12:15 ` [PATCH v2 11/15] crypto: Add userspace report for nivaead " Steffen Klassert
2011-08-17 12:16 ` [PATCH v2 12/15] crypto: Add userspace report for pcompress " Steffen Klassert
2011-08-17 12:16 ` [PATCH v2 13/15] crypto: Add userspace report for rng " Steffen Klassert
2011-08-17 12:17 ` [PATCH v2 14/15] crypto: Add userspace report for cipher " Steffen Klassert
2011-08-17 12:18 ` [PATCH v2 15/15] crypto: Add userspace report for compress " Steffen Klassert

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=20110817120936.GY16877@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).