Date: Mon, 13 Jul 2020 15:42:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 247954] geli: NULL encryption algorithm instapanics "IV_SEPARATE set when IV isn't used" Message-ID: <bug-247954-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247954 Bug ID: 247954 Summary: geli: NULL encryption algorithm instapanics "IV_SEPARATE set when IV isn't used" Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org Trying to create a geli provider with "-e NULL" instapanics on head at r362= 978. I'm guessing the panic was introduced by r359374. Sadly, geli's test suite does not cover that algorithm. I can't reproduce the panic on stable/12 at r361403. Steps to Reproduce: # sudo mdconfig -a -t malloc -s 4m md0 # sudo geli onetime -e NULL md0 panic: IV_SEPARATE set when IV isn't used cpuid =3D 0 time =3D 1594654462 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe006013b= a20 vpanic() at vpanic+0x182/frame 0xfffffe006013ba70 panic() at panic+0x43/frame 0xfffffe006013bad0 crypto_dispatch() at crypto_dispatch+0x682/frame 0xfffffe006013bb00 g_eli_crypto_run() at g_eli_crypto_run+0x1a6/frame 0xfffffe006013bb50 g_eli_worker() at g_eli_worker+0x368/frame 0xfffffe006013bbb0 fork_exit() at fork_exit+0x80/frame 0xfffffe006013bbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe006013bbf0 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247954-227>