From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v4 11/17] crypto: Add userspace report for givcipher type algorithms
Date: Tue, 27 Sep 2011 07:43:24 +0200 [thread overview]
Message-ID: <20110927054324.GN1808@secunet.com> (raw)
In-Reply-To: <20110927052050.GB1808@secunet.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
crypto/ablkcipher.c | 23 +++++++++++++++++++++++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/crypto/ablkcipher.c b/crypto/ablkcipher.c
index 5ea49ad..a816f24 100644
--- a/crypto/ablkcipher.c
+++ b/crypto/ablkcipher.c
@@ -457,6 +457,28 @@ static int crypto_init_givcipher_ops(struct crypto_tfm *tfm, u32 type,
return 0;
}
+static int crypto_givcipher_report(struct sk_buff *skb, struct crypto_alg *alg)
+{
+ struct crypto_report_blkcipher rblkcipher;
+
+ snprintf(rblkcipher.type, CRYPTO_MAX_ALG_NAME, "%s", "givcipher");
+ snprintf(rblkcipher.geniv, CRYPTO_MAX_ALG_NAME, "%s",
+ alg->cra_ablkcipher.geniv ?: "<built-in>");
+
+ rblkcipher.blocksize = alg->cra_blocksize;
+ rblkcipher.min_keysize = alg->cra_ablkcipher.min_keysize;
+ rblkcipher.max_keysize = alg->cra_ablkcipher.max_keysize;
+ rblkcipher.ivsize = alg->cra_ablkcipher.ivsize;
+
+ NLA_PUT(skb, CRYPTOCFGA_REPORT_BLKCIPHER,
+ sizeof(struct crypto_report_blkcipher), &rblkcipher);
+
+ return 0;
+
+nla_put_failure:
+ return -EMSGSIZE;
+}
+
static void crypto_givcipher_show(struct seq_file *m, struct crypto_alg *alg)
__attribute__ ((unused));
static void crypto_givcipher_show(struct seq_file *m, struct crypto_alg *alg)
@@ -479,6 +501,7 @@ const struct crypto_type crypto_givcipher_type = {
#ifdef CONFIG_PROC_FS
.show = crypto_givcipher_show,
#endif
+ .report = crypto_givcipher_report,
};
EXPORT_SYMBOL_GPL(crypto_givcipher_type);
--
1.7.0.4
next prev parent reply other threads:[~2011-09-27 5:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 5:20 [PATCH v4 00/17] crypto user configuration api Steffen Klassert
2011-09-27 5:21 ` [PATCH v4 01/17] crypto: Add a flag to identify crypto instances Steffen Klassert
2011-09-27 5:22 ` [PATCH v4 02/17] crypto: Export crypto_remove_spawns Steffen Klassert
2011-09-27 5:23 ` [PATCH v4 03/17] crypto: Export crypto_remove_final Steffen Klassert
2011-09-27 5:23 ` [PATCH v4 04/17] crypto: Add userspace configuration API Steffen Klassert
2011-09-27 5:24 ` [PATCH v4 05/17] crypto: Add a report function pointer to crypto_type Steffen Klassert
2011-09-27 5:25 ` [PATCH v4 06/17] crypto: Add userspace report for larval type algorithms Steffen Klassert
2011-09-27 5:26 ` [PATCH v4 07/17] crypto: Add userspace report for shash " Steffen Klassert
2011-09-27 5:41 ` [PATCH v4 08/17] crypto: Add userspace report for ahash " Steffen Klassert
2011-09-27 5:41 ` [PATCH v4 09/17] crypto: Add userspace report for blkcipher " Steffen Klassert
2011-09-27 5:42 ` [PATCH v4 10/17] crypto: Add userspace report for ablkcipher " Steffen Klassert
2011-09-27 5:43 ` Steffen Klassert [this message]
2011-09-27 5:44 ` [PATCH v4 12/17] crypto: Add userspace report for aead " Steffen Klassert
2011-11-02 14:25 ` Luis Henriques
2011-09-27 5:45 ` [PATCH v4 13/17] crypto: Add userspace report for nivaead " Steffen Klassert
2011-09-27 5:46 ` [PATCH v4 14/17] crypto: Add userspace report for pcompress " Steffen Klassert
2011-09-27 5:47 ` [PATCH v4 15/17] crypto: Add userspace report for rng " Steffen Klassert
2011-09-27 5:48 ` [PATCH v4 16/17] crypto: Add userspace report for cipher " Steffen Klassert
2011-09-27 5:48 ` [PATCH v4 17/17] crypto: Add userspace report for compress " Steffen Klassert
2011-10-21 12:38 ` [PATCH v4 00/17] crypto user configuration api Herbert Xu
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=20110927054324.GN1808@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).