From: kernel test robot <oliver.sang@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-crypto@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [crypto] 8b54e6a8f4: WARNING:at_crypto/testmgr.c:#alg_test
Date: Fri, 28 Mar 2025 16:51:38 +0800 [thread overview]
Message-ID: <202503281658.7a078821-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:at_crypto/testmgr.c:#alg_test" on:
commit: 8b54e6a8f4156ed43627f40300b0711dc977fbc1 ("crypto: testmgr - Add multibuffer hash testing")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master db8da9da41bced445077925f8a886c776a47440c]
in testcase: boot
config: x86_64-rhel-9.4-kunit
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+---------------------------------------+------------+------------+
| | 108ce629cf | 8b54e6a8f4 |
+---------------------------------------+------------+------------+
| WARNING:at_crypto/testmgr.c:#alg_test | 0 | 12 |
| RIP:alg_test | 0 | 12 |
+---------------------------------------+------------+------------+
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202503281658.7a078821-lkp@intel.com
[ 71.838087][ T2596] ------------[ cut here ]------------
[ 71.840212][ T2596] alg: self-tests for poly1305 using poly1305-simd failed (rc=-126)
[ 71.840238][ T2596] WARNING: CPU: 0 PID: 2596 at crypto/testmgr.c:5997 alg_test (crypto/testmgr.c:5997 (discriminator 1))
[ 71.842804][ T2596] Modules linked in:
[ 71.843503][ T2596] CPU: 0 UID: 0 PID: 2596 Comm: cryptomgr_test Not tainted 6.14.0-rc1-00186-g8b54e6a8f415 #1
[ 71.845159][ T2596] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 71.846781][ T2596] RIP: 0010:alg_test (crypto/testmgr.c:5997 (discriminator 1))
[ 71.847651][ T2596] Code: cc f7 ff ff 45 89 fd 44 39 ed 0f 8c fe f8 ff ff e9 de fc ff ff 44 89 c1 4c 89 ea 4c 89 f6 48 c7 c7 60 61 90 b7 e8 ac a6 01 ff <0f> 0b 44 8b 04 24 e9 66 fc ff ff 41 8d 6f 01 eb cc 48 8b 6c 24 18
All code
========
0: cc int3
1: f7 ff idiv %edi
3: ff 45 89 incl -0x77(%rbp)
6: fd std
7: 44 39 ed cmp %r13d,%ebp
a: 0f 8c fe f8 ff ff jl 0xfffffffffffff90e
10: e9 de fc ff ff jmp 0xfffffffffffffcf3
15: 44 89 c1 mov %r8d,%ecx
18: 4c 89 ea mov %r13,%rdx
1b: 4c 89 f6 mov %r14,%rsi
1e: 48 c7 c7 60 61 90 b7 mov $0xffffffffb7906160,%rdi
25: e8 ac a6 01 ff call 0xffffffffff01a6d6
2a:* 0f 0b ud2 <-- trapping instruction
2c: 44 8b 04 24 mov (%rsp),%r8d
30: e9 66 fc ff ff jmp 0xfffffffffffffc9b
35: 41 8d 6f 01 lea 0x1(%r15),%ebp
39: eb cc jmp 0x7
3b: 48 8b 6c 24 18 mov 0x18(%rsp),%rbp
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: 44 8b 04 24 mov (%rsp),%r8d
6: e9 66 fc ff ff jmp 0xfffffffffffffc71
b: 41 8d 6f 01 lea 0x1(%r15),%ebp
f: eb cc jmp 0xffffffffffffffdd
11: 48 8b 6c 24 18 mov 0x18(%rsp),%rbp
[ 71.854667][ T2596] RSP: 0018:ffffc9000072fd18 EFLAGS: 00010286
[ 71.855664][ T2596] RAX: 0000000000000000 RBX: ffffffffbacc4900 RCX: 1ffffffff70eba78
[ 71.856951][ T2596] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
[ 71.858195][ T2596] RBP: 1ffff920000e5faa R08: 0000000000000000 R09: fffffbfff70eba78
[ 71.859419][ T2596] R10: 0000000000000003 R11: 0000000000000001 R12: 00000000000000b7
[ 71.860650][ T2596] R13: ffff8881ab234000 R14: ffff8881ab234080 R15: 0000000000002dc0
[ 71.861880][ T2596] FS: 0000000000000000(0000) GS:ffff8883aee00000(0000) knlGS:0000000000000000
[ 71.863262][ T2596] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 71.864318][ T2596] CR2: 00007f68c26a3160 CR3: 000000000e66c000 CR4: 00000000000406f0
[ 71.865581][ T2596] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 71.866912][ T2596] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 71.868210][ T2596] Call Trace:
[ 71.868795][ T2596] <TASK>
[ 71.869314][ T2596] ? __warn (kernel/panic.c:748)
[ 71.869972][ T2596] ? alg_test (crypto/testmgr.c:5997 (discriminator 1))
[ 71.870752][ T2596] ? report_bug (lib/bug.c:180 lib/bug.c:219)
[ 71.871522][ T2596] ? handle_bug (arch/x86/kernel/traps.c:285)
[ 71.872255][ T2596] ? exc_invalid_op (arch/x86/kernel/traps.c:309 (discriminator 1))
[ 71.873050][ T2596] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:574)
[ 71.873884][ T2596] ? alg_test (crypto/testmgr.c:5997 (discriminator 1))
[ 71.874597][ T2596] ? alg_test (crypto/testmgr.c:5997 (discriminator 1))
[ 71.875322][ T2596] ? __pfx_alg_test (crypto/testmgr.c:5936)
[ 71.876084][ T2596] ? __pfx___schedule (kernel/sched/core.c:6645)
[ 71.876894][ T2596] ? try_to_wake_up (kernel/sched/core.c:4332)
[ 71.877689][ T2596] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162)
[ 71.878561][ T2596] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161)
[ 71.879484][ T2596] ? __pfx_cryptomgr_test (crypto/algboss.c:174)
[ 71.880305][ T2596] cryptomgr_test (crypto/algboss.c:181)
[ 71.881035][ T2596] kthread (kernel/kthread.c:464)
[ 71.881699][ T2596] ? __pfx_kthread (kernel/kthread.c:413)
[ 71.882452][ T2596] ? __pfx__raw_spin_lock_irq (kernel/locking/spinlock.c:169)
[ 71.883322][ T2596] ? __pfx_kthread (kernel/kthread.c:413)
[ 71.884067][ T2596] ret_from_fork (arch/x86/kernel/process.c:154)
[ 71.884800][ T2596] ? __pfx_kthread (kernel/kthread.c:413)
[ 71.885569][ T2596] ret_from_fork_asm (arch/x86/entry/entry_64.S:257)
[ 71.886338][ T2596] </TASK>
[ 71.886876][ T2596] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250328/202503281658.7a078821-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-28 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 8:51 kernel test robot [this message]
2025-03-30 1:43 ` [PATCH] Revert "crypto: testmgr - Add multibuffer hash testing" 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=202503281658.7a078821-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).