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 v4 05/17] crypto: Add a report function pointer to crypto_type
Date: Tue, 27 Sep 2011 07:24:29 +0200	[thread overview]
Message-ID: <20110927052429.GG1808@secunet.com> (raw)
In-Reply-To: <20110927052050.GB1808@secunet.com>

We add a report function pointer to struct crypto_type. This function
pointer is used from the crypto userspace configuration API to report
crypto algorithms to userspace.

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

diff --git a/crypto/crypto_user.c b/crypto/crypto_user.c
index 513cfe7..aa67c74 100644
--- a/crypto/crypto_user.c
+++ b/crypto/crypto_user.c
@@ -84,6 +84,11 @@ static int crypto_report_one(struct crypto_alg *alg,
 
 	NLA_PUT_U32(skb, CRYPTOCFGA_PRIORITY_VAL, alg->cra_priority);
 
+	if (alg->cra_type && alg->cra_type->report) {
+		if (alg->cra_type->report(skb, alg))
+			goto nla_put_failure;
+	}
+
 	return 0;
 
 nla_put_failure:
diff --git a/include/crypto/algapi.h b/include/crypto/algapi.h
index 59c3e5b..ecc721d 100644
--- a/include/crypto/algapi.h
+++ b/include/crypto/algapi.h
@@ -15,6 +15,7 @@
 #include <linux/crypto.h>
 #include <linux/list.h>
 #include <linux/kernel.h>
+#include <linux/skbuff.h>
 
 struct module;
 struct rtattr;
@@ -26,6 +27,7 @@ struct crypto_type {
 	int (*init)(struct crypto_tfm *tfm, u32 type, u32 mask);
 	int (*init_tfm)(struct crypto_tfm *tfm);
 	void (*show)(struct seq_file *m, struct crypto_alg *alg);
+	int (*report)(struct sk_buff *skb, struct crypto_alg *alg);
 	struct crypto_alg *(*lookup)(const char *name, u32 type, u32 mask);
 
 	unsigned int type;
-- 
1.7.0.4

  parent reply	other threads:[~2011-09-27  5:24 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 ` Steffen Klassert [this message]
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 ` [PATCH v4 11/17] crypto: Add userspace report for givcipher " Steffen Klassert
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=20110927052429.GG1808@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).