From: "Stephan Müller" <smueller@chronox.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Mat Martineau <mathew.j.martineau@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [security] d3b04a4398: WARNING:at_crypto/kdf_sp800108.c:#crypto_kdf108_init
Date: Sun, 05 Dec 2021 11:21:56 +0100 [thread overview]
Message-ID: <3438006.aCxCBeP46V@positron.chronox.de> (raw)
In-Reply-To: <20211130080419.GC29514@xsang-OptiPlex-9020>
Am Dienstag, 30. November 2021, 09:04:19 CET schrieb kernel test robot:
Hi,
...
>
>
> +------------------------------------------------------+------------+-------
> -----+
> | | d792134423 |
> | | d3b04a4398 |
>
> +------------------------------------------------------+------------+-------
> -----+
> | boot_successes | 14 | 0
> | | boot_failures | 0 |
> | 16 | WARNING:at_crypto/kdf_sp800108.c:#crypto_kdf108_init | 0
> | | 16 | EIP:crypto_kdf108_init
> | | 0 | 16 |
> +------------------------------------------------------+------------+-------
> -----+
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
> [ 18.648980][ T1] WARNING: CPU: 0 PID: 1 at crypto/kdf_sp800108.c:138
> crypto_kdf108_init (crypto/kdf_sp800108.c:136) [ 18.649900][ T1]
> Modules linked in:
The issue is that the self-test fails for 16 out of 30 times, i.e. it is kind
of random when it happens or not.
I am unable to reproduce it with i386 and clang-13. I can also not reproduce
it with GCC.
Nor do I see an obvious issue in the code that points to either uninitizlized
memory or otherwise could affect the test result.
I keep trying with Clang-14
Ciao
Stephan
next prev parent reply other threads:[~2021-12-05 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 8:04 kernel test robot
2021-12-05 10:21 ` Stephan Müller [this message]
2021-12-10 2:54 ` Yujie Liu
2021-12-10 14:16 ` Stephan Mueller
2021-12-17 4:14 ` Herbert Xu
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=3438006.aCxCBeP46V@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=oliver.sang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox