From: kernel test robot <oliver.sang@intel.com>
To: Leonid Ravich <lravich@amazon.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-raid@vger.kernel.org>, <dm-devel@lists.linux.dev>,
<linux-crypto@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <ebiggers@kernel.org>,
<snitzer@kernel.org>, <mpatocka@redhat.com>, <axboe@kernel.dk>,
<oliver.sang@intel.com>
Subject: Re: [PATCH v5 4/5] dm crypt: batch a bio segment's sectors via dun()
Date: Thu, 16 Jul 2026 21:34:21 +0800 [thread overview]
Message-ID: <202607161535.5e935cc3-lkp@intel.com> (raw)
In-Reply-To: <20260630083431.2772-5-lravich@amazon.com>
Hello,
kernel test robot noticed "RIP:alg_test.cold" on:
commit: 89bd605959ed9145ac2906d1cc4357b71eee9d3b ("[PATCH v5 4/5] dm crypt: batch a bio segment's sectors via dun()")
url: https://github.com/intel-lab-lkp/linux/commits/Leonid-Ravich/crypto-skcipher-add-per-request-data_unit_size/20260701-185738
patch link: https://lore.kernel.org/all/20260630083431.2772-5-lravich@amazon.com/
patch subject: [PATCH v5 4/5] dm crypt: batch a bio segment's sectors via dun()
in testcase: kunit
version:
with following parameters:
group: group-00
config: x86_64-rhel-9.4-kunit
compiler: gcc-14
test machine: 10 threads 1 sockets Intel(R) Core Ultra Series 3 @ 3.20GHz (Panther Lake) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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/202607161535.5e935cc3-lkp@intel.com
kern :warn : [ 136.442332] [ T2675] ------------[ cut here ]------------
kern :warn : [ 136.442345] [ T2675] alg: self-tests for cbc(aes) using cbc-aes-aesni failed (rc=-110)
kern :warn : [ 136.442348] [ T2675] WARNING: crypto/testmgr.c:6087 at alg_test.cold+0x9c/0xb1, CPU#5: cryptomgr_test/2675
kern :warn : [ 136.442364] [ T2675] Modules linked in: dun
kern :warn : [ 136.442373] [ T2675] CPU: 5 UID: 0 PID: 2675 Comm: cryptomgr_test Not tainted 7.1.0-rc3+ #1 PREEMPT(lazy)
kern :warn : [ 136.442382] [ T2675] Hardware name: Intel Corporation Panther Lake Client Platform/PTL-UH LP5 T3 RVP1, BIOS PTLPFWI1.R00.3332.D01.2508190102 08/19/2025
kern :warn : [ 136.442389] [ T2675] RIP: 0010:alg_test.cold (testmgr.c:6087 (discriminator 1))
kern :warn : [ 136.442395] [ T2675] Code: 89 de 48 c7 c7 e0 44 93 84 e8 9b c2 fb ff 41 83 fc fe 0f 84 b1 e8 43 01 48 8d 3d 7a 80 85 05 48 8b 54 24 08 44 89 e1 48 89 de <67> 48 0f b9 3a e9 95 e8 43 01 48 8b 14 24 b8 ff ff 37 00 48 c1 e0
All code
========
0: 89 de mov %ebx,%esi
2: 48 c7 c7 e0 44 93 84 mov $0xffffffff849344e0,%rdi
9: e8 9b c2 fb ff call 0xfffffffffffbc2a9
e: 41 83 fc fe cmp $0xfffffffe,%r12d
12: 0f 84 b1 e8 43 01 je 0x143e8c9
18: 48 8d 3d 7a 80 85 05 lea 0x585807a(%rip),%rdi # 0x5858099
1f: 48 8b 54 24 08 mov 0x8(%rsp),%rdx
24: 44 89 e1 mov %r12d,%ecx
27: 48 89 de mov %rbx,%rsi
2a:* 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: e9 95 e8 43 01 jmp 0x143e8c9
34: 48 8b 14 24 mov (%rsp),%rdx
38: b8 ff ff 37 00 mov $0x37ffff,%eax
3d: 48 rex.W
3e: c1 .byte 0xc1
3f: e0 .byte 0xe0
Code starting with the faulting instruction
===========================================
0: 67 48 0f b9 3a ud1 (%edx),%rdi
5: e9 95 e8 43 01 jmp 0x143e89f
a: 48 8b 14 24 mov (%rsp),%rdx
e: b8 ff ff 37 00 mov $0x37ffff,%eax
13: 48 rex.W
14: c1 .byte 0xc1
15: e0 .byte 0xe0
kern :warn : [ 136.442404] [ T2675] RSP: 0018:ffffc9000219fce0 EFLAGS: 00010293
kern :warn : [ 136.442411] [ T2675] RAX: 0000000000000041 RBX: ffff888474e11480 RCX: 00000000ffffff92
kern :warn : [ 136.442416] [ T2675] RDX: ffff888474e11400 RSI: ffff888474e11480 RDI: ffffffff86abc5a0
kern :warn : [ 136.442421] [ T2675] RBP: 1ffff92000433fa5 R08: 0000000000000000 R09: fffffbfff0b2b848
kern :warn : [ 136.442426] [ T2675] R10: 0000000000000003 R11: fefefefefefefeff R12: 00000000ffffff92
kern :warn : [ 136.442431] [ T2675] R13: dffffc0000000000 R14: 0000000000000069 R15: 0000000000000027
kern :warn : [ 136.442436] [ T2675] FS: 0000000000000000(0000) GS:ffff88848572b000(0000) knlGS:0000000000000000
kern :warn : [ 136.442442] [ T2675] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kern :warn : [ 136.442446] [ T2675] CR2: 00007fc9e48120ac CR3: 000000047c074001 CR4: 0000000108770ef0
kern :warn : [ 136.442451] [ T2675] PKRU: 55555554
kern :warn : [ 136.442455] [ T2675] Call Trace:
kern :warn : [ 136.442458] [ T2675] <TASK>
kern :warn : [ 136.442464] [ T2675] ? __pfx_alg_test (linux/crypto.h:449)
kern :warn : [ 136.442470] [ T2675] ? kasan_save_track (kasan/common.c:78)
kern :warn : [ 136.442477] [ T2675] ? _raw_spin_lock_irqsave (linux/instrumented.h:55 linux/atomic/atomic-instrumented.h:1301 asm-generic/qspinlock.h:111 linux/spinlock.h:187 linux/spinlock_api_smp.h:133 locking/spinlock.c:166)
kern :warn : [ 136.442483] [ T2675] ? __pfx__raw_spin_lock_irqsave (locking/spinlock.c:273)
kern :warn : [ 136.442489] [ T2675] ? __pfx_cryptomgr_test (usercopy_64.c:?)
kern :warn : [ 136.442496] [ T2675] ? kthread_affine_node (kthread.c:377)
kern :warn : [ 136.442501] [ T2675] ? __kthread_parkme (linux/instrumented.h:82 asm-generic/bitops/instrumented-non-atomic.h:141 kthread.c:272)
kern :warn : [ 136.442508] [ T2675] ? __pfx_cryptomgr_test (usercopy_64.c:?)
kern :warn : [ 136.442513] [ T2675] cryptomgr_test (algboss.c:179)
kern :warn : [ 136.442519] [ T2675] kthread (kthread.c:436)
kern :warn : [ 136.442523] [ T2675] ? recalc_sigpending (linux/instrumented.h:97 asm-generic/bitops/instrumented-atomic.h:41 linux/thread_info.h:109 signal.c:181)
kern :warn : [ 136.442530] [ T2675] ? __pfx_kthread (linux/list.h:381 (discriminator 2))
kern :warn : [ 136.442534] [ T2675] ret_from_fork (x86/kernel/process.c:158)
kern :warn : [ 136.442541] [ T2675] ? __pfx_ret_from_fork (x86/include/asm/entry-common.h:54)
kern :warn : [ 136.442547] [ T2675] ? switch_fpu (linux/instrumented.h:82 asm-generic/bitops/instrumented-non-atomic.h:141 linux/thread_info.h:133 linux/sched.h:2069 x86/include/asm/fpu/sched.h:34)
kern :warn : [ 136.442553] [ T2675] ? __switch_to (x86/kernel/process_64.c:403 x86/kernel/process_64.c:663)
kern :warn : [ 136.442558] [ T2675] ? __pfx_kthread (linux/list.h:381 (discriminator 2))
kern :warn : [ 136.442563] [ T2675] ret_from_fork_asm (x86/entry/entry_64.S:245)
kern :warn : [ 136.442570] [ T2675] </TASK>
kern :warn : [ 136.442573] [ T2675] ---[ end trace 0000000000000000 ]---
kern :err : [ 136.442580] [ T2675] alg: Unexpected test result for cbc-aes-aesni: -110
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260716/202607161535.5e935cc3-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-07-16 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 8:34 [PATCH v5 0/5] crypto: skcipher - multi-data-unit dispatch as a template Leonid Ravich
2026-06-30 8:34 ` [PATCH v5 1/5] crypto: skcipher - add per-request data_unit_size Leonid Ravich
2026-07-13 2:19 ` Herbert Xu
2026-06-30 8:34 ` [PATCH v5 2/5] crypto: dun - data-unit-number dispatch template Leonid Ravich
2026-07-13 2:25 ` Herbert Xu
2026-07-15 12:01 ` Leonid Ravich
2026-06-30 8:34 ` [PATCH v5 3/5] crypto: testmgr - test dun() dispatch Leonid Ravich
2026-06-30 8:34 ` [PATCH v5 4/5] dm crypt: batch a bio segment's sectors via dun() Leonid Ravich
2026-07-16 13:34 ` kernel test robot [this message]
2026-07-01 6:53 ` [PATCH v5 5/5] blk-crypto: fallback - batch a segment's data units " Leonid Ravich
2026-07-01 7:19 ` [PATCH v5 0/5] crypto: skcipher - multi-data-unit dispatch as a template Eric Biggers
2026-07-02 8:45 ` Leonid Ravich
2026-07-02 16:45 ` 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=202607161535.5e935cc3-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lravich@amazon.com \
--cc=mpatocka@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=snitzer@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 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.