Bug ID | 1195768 |
---|---|
Summary | ppc64le: alg: skcipher: failed to allocate transform for p8_aes_xts: -2 |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Kernel |
Assignee | kernel-bugs@opensuse.org |
Reporter | petr.vorel@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
There is kernel oops on Tumbleweed ppc64le kernel: [ 0.295853][ T83] Failed to allocate xts(aes) fallback: -2 [ 0.296710][ T83] alg: skcipher: failed to allocate transform for p8_aes_xts: -2 [ 0.297525][ T83] ------------[ cut here ]------------ [ 0.298310][ T83] alg: self-tests for p8_aes_xts (xts(aes)) failed (rc=-2) [ 0.298325][ T83] WARNING: CPU: 2 PID: 83 at crypto/testmgr.c:5681 alg_test+0x8a8/0xd80 [ 0.299990][ T83] Modules linked in: [ 0.300796][ T83] CPU: 2 PID: 83 Comm: cryptomgr_test Not tainted 5.16.4-1-default #1 openSUSE Tumbleweed 514f0c059e014af0dbaa3c399367e9fbb58fffc9 [ 0.302511][ T83] NIP: c00000000077ba08 LR: c00000000077ba04 CTR: c0000000008ea730 [ 0.303410][ T83] REGS: c0000000060bf960 TRAP: 0700 Not tainted (5.16.4-1-default) [ 0.304309][ T83] MSR: 800000000282b033 <SF,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 28008221 XER: 20000000 [ 0.305243][ T83] CFAR: c00000000015ba50 IRQMASK: 0 [ 0.305243][ T83] GPR00: c00000000077ba04 c0000000060bfc00 c000000002968a00 0000000000000038 [ 0.305243][ T83] GPR04: 00000000ffffbfff c0000000060bf8c0 c0000000060bf8b8 0000000000000000 [ 0.305243][ T83] GPR08: c000000002807148 c000000002647060 c000000002647060 0000000048008221 [ 0.305243][ T83] GPR12: c0000000027a7108 c00000003fffd680 c00000000019a858 c000000002d4cdc0 [ 0.305243][ T83] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 0.305243][ T83] GPR20: 0000000000000000 00000000000000a6 c000000000f7dd00 00000000000000a5 [ 0.305243][ T83] GPR24: 00000000000000a5 fffffffffffffffe 0000000000003240 c000000002bff140 [ 0.305243][ T83] GPR28: 0000000000000400 0000000000000105 c000000004b8ca80 c000000004b8ca00 [ 0.313426][ T83] NIP [c00000000077ba08] alg_test+0x8a8/0xd80 [ 0.314280][ T83] LR [c00000000077ba04] alg_test+0x8a4/0xd80 [ 0.315134][ T83] Call Trace: [ 0.316020][ T83] [c0000000060bfc00] [c00000000077ba04] alg_test+0x8a4/0xd80 (unreliable) [ 0.316927][ T83] [c0000000060bfd70] [c000000000777f34] cryptomgr_test+0x44/0x80 [ 0.317823][ T83] [c0000000060bfda0] [c00000000019aa08] kthread+0x1b8/0x1c0 [ 0.318714][ T83] [c0000000060bfe10] [c00000000000cf64] ret_from_kernel_thread+0x5c/0x64 [ 0.319606][ T83] Instruction dump: [ 0.320454][ T83] 3d220029 8929676a 2c090000 40820414 7f3907b4 3c62fe93 7fc5f378 7fe4fb78 [ 0.321391][ T83] 38630dc8 7f26cb78 4b9dffe9 60000000 <0fe00000> fa2100f8 fa410100 fa610108 [ 0.322318][ T83] ---[ end trace 8d7a5ba1cc312459 ]--- System boots and this is just crypto testing API, but tainting kernel just during boot is bad enough to get fixed. I suspect it's upstream issue (haven't tested it on mainline kernel), because we don't have in Tumbleweed these FIPS specific patches from SLES and system booted without fips being enabled. Thus I can report it to linux-crypto ML