[Bug 228458] [jail] panic: _mtx_lock_sleep: recursed on non-recursive mutex unp @ /usr/src/sys/kern/uipc_usrreq.c:354

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu May 24 13:06:02 UTC 2018


            Bug ID: 228458
           Summary: [jail] panic: _mtx_lock_sleep: recursed on
                    non-recursive mutex unp @
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: marieheleneka at gmail.com

Created attachment 193649
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193649&action=edit
Screenshot of kernel panic

This panic always occurs when starting jails, regardless of whether it's during
boot or some time after (i.e. jail_enabled=NO, service jail onestart)

There is also a lock order reversal between "allprison" and
"vnet_sysinit_sxlock" (see screenshot)

=== Infodump ===

# uname -a
FreeBSD venus 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334115: Thu May 24 00:08:59
CEST 2018     root at venus:/usr/obj/usr/src/amd64.amd64/sys/Venus  amd64

# cat /usr/src/sys/amd64/conf/Venus
include GENERIC
ident Venus

options VIMAGE

device epair

# cat /etc/jail.conf
exec.start              = "/bin/sh /etc/rc";
exec.stop               = "/bin/sh /etc/rc.shutdown";
mount.fstab             = "/etc/fstab.$name";
path                    = "/usr/jails/$name";
host.hostname           = "$name.mhka.no";

devsamba {
  vnet.interface            = "epair0b";

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list