[Bug 247954] geli: NULL encryption algorithm instapanics "IV_SEPARATE set when IV isn't used"
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Jul 13 15:42:09 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247954
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 at FreeBSD.org
Reporter: asomers at FreeBSD.org
Trying to create a geli provider with "-e NULL" instapanics on head at r362978.
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 = 0
time = 1594654462
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe006013ba20
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
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list