Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Apr 2021 19:55:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 255131] kernel panic using zfs on shsec
Message-ID:  <bug-255131-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255131

            Bug ID: 255131
           Summary: kernel panic using zfs on shsec
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: nvass@gmx.com

Trying to use zfs on a shsec device will result to a kernel panic.

Use the following script to reproduce the problem:
#!/bin/sh
gshsec load
m0=3D`mdconfig -at swap -s 120M`
m1=3D`mdconfig -at swap -s 120M`
m2=3D`mdconfig -at swap -s 120M`

gshsec label secret1234 $m0 $m1 $m2
zpool create secret1234 /dev/shsec/secret1234



Panic message:
Unread portion of the kernel message buffer:
panic: non-NULL bp->data in g_io_request(cmd=3D5)
cpuid =3D 1
time =3D 1618601239
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0063abf=
a30
vpanic() at vpanic+0x181/frame 0xfffffe0063abfa80
panic() at panic+0x43/frame 0xfffffe0063abfae0
g_io_request() at g_io_request+0x365/frame 0xfffffe0063abfb10
g_shsec_start() at g_shsec_start+0x1db/frame 0xfffffe0063abfb70
g_io_schedule_down() at g_io_schedule_down+0x134/frame 0xfffffe0063abfba0
g_down_procbody() at g_down_procbody+0x5c/frame 0xfffffe0063abfbb0
fork_exit() at fork_exit+0x80/frame 0xfffffe0063abfbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0063abfbf0
--- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 ---
KDB: enter: panic

--=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-255131-227>