From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v4 02/17] crypto: Export crypto_remove_spawns
Date: Tue, 27 Sep 2011 07:22:08 +0200 [thread overview]
Message-ID: <20110927052208.GD1808@secunet.com> (raw)
In-Reply-To: <20110927052050.GB1808@secunet.com>
The upcomming crypto usrerspace configuration api needs
to remove the spawns on top on an algorithm, so export
crypto_remove_spawns.
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
crypto/algapi.c | 6 +++---
crypto/internal.h | 2 ++
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/crypto/algapi.c b/crypto/algapi.c
index 6fd9bcf..1b54d74 100644
--- a/crypto/algapi.c
+++ b/crypto/algapi.c
@@ -129,9 +129,8 @@ static void crypto_remove_spawn(struct crypto_spawn *spawn,
BUG_ON(!list_empty(&inst->alg.cra_users));
}
-static void crypto_remove_spawns(struct crypto_alg *alg,
- struct list_head *list,
- struct crypto_alg *nalg)
+void crypto_remove_spawns(struct crypto_alg *alg, struct list_head *list,
+ struct crypto_alg *nalg)
{
u32 new_type = (nalg ?: alg)->cra_flags;
struct crypto_spawn *spawn, *n;
@@ -177,6 +176,7 @@ static void crypto_remove_spawns(struct crypto_alg *alg,
crypto_remove_spawn(spawn, list);
}
}
+EXPORT_SYMBOL_GPL(crypto_remove_spawns);
static struct crypto_larval *__crypto_register_alg(struct crypto_alg *alg)
{
diff --git a/crypto/internal.h b/crypto/internal.h
index d4384b0..b6dcb31 100644
--- a/crypto/internal.h
+++ b/crypto/internal.h
@@ -86,6 +86,8 @@ struct crypto_alg *crypto_larval_lookup(const char *name, u32 type, u32 mask);
void crypto_larval_error(const char *name, u32 type, u32 mask);
void crypto_alg_tested(const char *name, int err);
+void crypto_remove_spawns(struct crypto_alg *alg, struct list_head *list,
+ struct crypto_alg *nalg);
void crypto_shoot_alg(struct crypto_alg *alg);
struct crypto_tfm *__crypto_alloc_tfm(struct crypto_alg *alg, u32 type,
u32 mask);
--
1.7.0.4
next prev parent reply other threads:[~2011-09-27 5:22 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 ` Steffen Klassert [this message]
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 ` [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=20110927052208.GD1808@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).