path: root/crypto/algapi.c
diff options
authorHerbert Xu <herbert@gondor.apana.org.au>2007-10-02 22:27:29 +0800
committerDavid S. Miller <davem@sunset.davemloft.net>2007-10-10 16:55:47 -0700
commitd8058480b35dbc3d1e6085b3f13b80af27def09e (patch)
treef343b65876738ba5c0abd8de413a6b076a5af928 /crypto/algapi.c
parent70613783fc0f6e37b442d79e8417f71a2b71ed93 (diff)
[CRYPTO] api: Explain the comparison on larval cra_name
This patch adds a comment to explain why we compare the cra_driver_name of the algorithm being registered against the cra_name of a larval as opposed to the cra_driver_name of the larval. In fact larvals have only one name, cra_name which is the name that was requested by the user. The test here is simply trying to find out whether the algorithm being registered can or can not satisfy the larval. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/algapi.c')
1 files changed, 5 insertions, 0 deletions
diff --git a/crypto/algapi.c b/crypto/algapi.c
index 58cc1916480..8ff8c2656d9 100644
--- a/crypto/algapi.c
+++ b/crypto/algapi.c
@@ -149,6 +149,11 @@ static int __crypto_register_alg(struct crypto_alg *alg,
if (crypto_is_larval(q)) {
struct crypto_larval *larval = (void *)q;
+ /*
+ * Check to see if either our generic name or
+ * specific name can satisfy the name requested
+ * by the larval entry q.
+ */
if (strcmp(alg->cra_name, q->cra_name) &&
strcmp(alg->cra_driver_name, q->cra_name))