From: Michal Ludvig <michal@logix.cz>
Date: Tue, 30 May 2006 04:49:38 +0000 (+1000)
Subject: [CRYPTO] tcrypt: Return -EAGAIN from module_init()
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=14fdf477a7e3ff54f8e67fe506dd2677a36c56e4;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git

[CRYPTO] tcrypt: Return -EAGAIN from module_init()

Intentionaly return -EAGAIN from module_init() to ensure
it doesn't stay loaded in the kernel.  The module does all
its work from init() and doesn't offer any runtime
functionality => we don't need it in the memory, do we?

Signed-off-by: Michal Ludvig <michal@logix.cz>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
---

diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index 49e344f00806..7bf93c5decfe 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -1113,7 +1113,14 @@ static int __init init(void)
 
 	kfree(xbuf);
 	kfree(tvmem);
-	return 0;
+
+	/* We intentionaly return -EAGAIN to prevent keeping
+	 * the module. It does all its work from init()
+	 * and doesn't offer any runtime functionality 
+	 * => we don't need it in the memory, do we?
+	 *                                        -- mludvig
+	 */
+	return -EAGAIN;
 }
 
 /*