All of lore.kernel.org
 help / color / mirror / Atom feed
From: wenyehai via ltp <ltp@lists.linux.it>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: [LTP] 答复:  [PATCH] add several hash algorithms for crypto/crypto_user02.c
Date: Mon, 10 Jan 2022 03:59:39 +0000	[thread overview]
Message-ID: <0035845766004452880d56963135c616@huawei.com> (raw)
In-Reply-To: <YdW1m4D2wLYQm1v/@sol.localdomain>


[-- Attachment #1.1.1: Type: text/plain, Size: 2544 bytes --]

Hi Eric:



Thank you very much for your kind reply, and I am very sorry for not describing the background clearly.



Actually, I wanted to test the sha3 algorithm in kernel 5.10, but crypto_user02.c return "no viable algorithm found" as follows:



[cid:image001.png@01D80618.14306F90]



So I add sha3 to crypto_user02.c and run again, at the same time, according to the latest linux kernel encryption module, add several hash algorithms, as follows:



[cid:image002.png@01D80618.F702D790]







Best Regards

Yehai Wen







-----邮件原件-----

发件人: Eric Biggers [mailto:ebiggers@kernel.org]

发送时间: 2022年1月5日 23:14

收件人: wenyehai <wenyehai@huawei.com>

抄送: ltp@lists.linux.it

主题: Re: [LTP] [PATCH] add several hash algorithms for crypto/crypto_user02.c



On Tue, Jan 04, 2022 at 05:15:29PM +0800, wenyehai via ltp wrote:

> kernel/crypto/crypto_user02.c: add several hash algorithms according

> to the latest linux kernel encryption module

>

> Signed-off-by: Yehai Wen <wenyehai@huawei.com>

> ---

>  testcases/kernel/crypto/crypto_user02.c | 10 +++++++++-

>  1 file changed, 9 insertions(+), 1 deletion(-)

>

> diff --git a/testcases/kernel/crypto/crypto_user02.c

> b/testcases/kernel/crypto/crypto_user02.c

> index 717b297..afaff5d 100644

> --- a/testcases/kernel/crypto/crypto_user02.c

> +++ b/testcases/kernel/crypto/crypto_user02.c

> @@ -40,7 +40,15 @@ static const char * const ALGORITHM_CANDIDATES[] = {

>    "hmac(sha256-generic)",

>    "hmac(sha384-generic)",

>    "hmac(md5-generic)",

> -     "hmac(sm3-generic)"

> +    "hmac(sm3-generic)",

> +    "hmac(sha512-generic)",

> +    "hmac(rmd160-generic)",

> +    "hmac(sha3-224-generic)",

> +    "hmac(sha3-256-generic)",

> +    "hmac(sha3-384-generic)",

> +    "hmac(sha3-512-generic)",

> +    "hmac(streebog256-generic)",

> +    "hmac(streebog512-generic)"

>  };



There's no harm in listing more algorithms here.  Just to avoid any misunderstanding though, are you expecting this test to test those algorithms?

This test just uses the first available algorithm listed; it's a regression test for a bug in the crypto_user API, and not a test for the algorithms themselves.

So, listing more algorithms here doesn't magically provide test coverage for them.  If what you're looking for is an LTP test that tests that certain algorithms are working correctly, then such a test would need to be written.



- Eric

[-- Attachment #1.1.2: Type: text/html, Size: 9877 bytes --]

[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 8768 bytes --]

[-- Attachment #1.3: image002.png --]
[-- Type: image/png, Size: 31414 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-01-10  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04  9:15 [LTP] [PATCH] add several hash algorithms for crypto/crypto_user02.c wenyehai via ltp
2022-01-05 15:13 ` Eric Biggers
2022-01-10  3:59   ` wenyehai via ltp [this message]
2022-01-10 17:44     ` [LTP] 答复: " Eric Biggers
2022-01-11  2:19       ` [LTP] 答复: " wenyehai via ltp
2022-01-11  3:03         ` Eric Biggers
2022-01-11  3:11           ` [LTP] 答复: " wenyehai via ltp

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=0035845766004452880d56963135c616@huawei.com \
    --to=ltp@lists.linux.it \
    --cc=ebiggers@kernel.org \
    --cc=wenyehai@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.