From: "Chen Li" <chenli@uniontech.com>
To: herbert <herbert@gondor.apana.org.au>,
davem <davem@davemloft.net>,
linux-crypto <linux-crypto@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] crypto: lib/sha256 - add sha256_value function
Date: Sat, 7 Aug 2021 11:04:51 +0800 [thread overview]
Message-ID: <tencent_68FC194846DCFC8653D8D915@qq.com> (raw)
Add a function sha256_value() which accepts a string and store SHA256 hash
of this string into dest.
Signed-off-by: Chen Li <chenli@uniontech.com>
---
include/crypto/sha2.h | 1 +
lib/crypto/sha256.c | 23 +++++++++++++++++++++++
2 files changed, 24 insertions(+)
diff --git a/include/crypto/sha2.h b/include/crypto/sha2.h
index 2838f529f31e..ce17954cab38 100644
--- a/include/crypto/sha2.h
+++ b/include/crypto/sha2.h
@@ -115,6 +115,7 @@ static inline void sha256_init(struct sha256_state *sctx)
void sha256_update(struct sha256_state *sctx, const u8 *data, unsigned int len);
void sha256_final(struct sha256_state *sctx, u8 *out);
void sha256(const u8 *data, unsigned int len, u8 *out);
+int sha256_value(u8 **dest, const u8 *src);
static inline void sha224_init(struct sha256_state *sctx)
{
diff --git a/lib/crypto/sha256.c b/lib/crypto/sha256.c
index 72a4b0b1df28..ce1de7a3e32e 100644
--- a/lib/crypto/sha256.c
+++ b/lib/crypto/sha256.c
@@ -13,6 +13,8 @@
#include <linux/bitops.h>
#include <linux/export.h>
+#include <linux/mm.h>
+#include <linux/slab.h>
#include <linux/module.h>
#include <linux/string.h>
#include <crypto/sha2.h>
@@ -206,4 +208,25 @@ void sha256(const u8 *data, unsigned int len, u8 *out)
}
EXPORT_SYMBOL(sha256);
+int sha256_value(u8 **dest, const u8 *src)
+{
+ u8 out[SHA256_DIGEST_SIZE];
+ int i, k;
+ unsigned char hex[2];
+
+ *dest = kvmalloc(sizeof(u8) * (SHA256_BLOCK_SIZE + 1), GFP_KERNEL);
+ if (ZERO_OR_NULL_PTR(*dest))
+ return -ENOMEM;
+ sha256(src, strlen(src), out);
+
+ for (i = 0, k = 0; i < SHA256_DIGEST_SIZE; i++) {
+ sprintf(hex, "%02x", out[i]);
+ (*dest)[k++] = hex[0];
+ (*dest)[k++] = hex[1];
+ }
+ (*dest)[k] = '\0';
+ return 0;
+}
+EXPORT_SYMBOL(sha256_value);
+
MODULE_LICENSE("GPL");
--
2.32.0.93.g670b81a890
next reply other threads:[~2021-08-07 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 3:04 Chen Li [this message]
2021-08-07 3:06 Chen Li
2021-08-07 5:33 ` Eric Biggers
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=tencent_68FC194846DCFC8653D8D915@qq.com \
--to=chenli@uniontech.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®