aboutsummaryrefslogtreecommitdiffstats
path: root/module/icp/io/sha1_mod.c
diff options
context:
space:
mode:
Diffstat (limited to 'module/icp/io/sha1_mod.c')
-rw-r--r--module/icp/io/sha1_mod.c27
1 files changed, 2 insertions, 25 deletions
diff --git a/module/icp/io/sha1_mod.c b/module/icp/io/sha1_mod.c
index 5a372e3d3..ebd6b1f29 100644
--- a/module/icp/io/sha1_mod.c
+++ b/module/icp/io/sha1_mod.c
@@ -25,7 +25,6 @@
*/
#include <sys/zfs_context.h>
-#include <sys/modctl.h>
#include <sys/crypto/common.h>
#include <sys/crypto/icp.h>
#include <sys/crypto/spi.h>
@@ -34,25 +33,6 @@
#include <sha1/sha1_impl.h>
/*
- * The sha1 module is created with two modlinkages:
- * - a modlmisc that allows consumers to directly call the entry points
- * SHA1Init, SHA1Update, and SHA1Final.
- * - a modlcrypto that allows the module to register with the Kernel
- * Cryptographic Framework (KCF) as a software provider for the SHA1
- * mechanisms.
- */
-
-static struct modlcrypto modlcrypto = {
- &mod_cryptoops,
- "SHA1 Kernel SW Provider 1.1"
-};
-
-static struct modlinkage modlinkage = {
- MODREV_1, { &modlcrypto, NULL }
-};
-
-
-/*
* Macros to access the SHA1 or SHA1-HMAC contexts from a context passed
* by KCF to one of the entry points.
*/
@@ -189,9 +169,6 @@ sha1_mod_init(void)
{
int ret;
- if ((ret = mod_install(&modlinkage)) != 0)
- return (ret);
-
/*
* Register with KCF. If the registration fails, log an
* error but do not uninstall the module, since the functionality
@@ -208,7 +185,7 @@ sha1_mod_init(void)
int
sha1_mod_fini(void)
{
- int ret;
+ int ret = 0;
if (sha1_prov_handle != 0) {
if ((ret = crypto_unregister_provider(sha1_prov_handle)) !=
@@ -221,7 +198,7 @@ sha1_mod_fini(void)
sha1_prov_handle = 0;
}
- return (mod_remove(&modlinkage));
+ return (ret);
}
/*