[Bug 222314] VNET jail panics kernel (arm64)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222314

            Bug ID: 222314
           Summary: VNET jail panics kernel (arm64)
           Product: Base System
           Version: 11.1-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: heinz at project-fifo.net

Starting a jail with vnets panics the kernel, this is not a duplicate of
#213896 as the patch mentioned there was applied to the kernel in question.

I'm not sure weather or not it is a arm64 related issue or not, it is a arm64
system but the nic used is a normal intel nic.

login: lock order reversal:
 1st 0xfffffd0094344418 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:849
 2nd 0xfffffd0094344240 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2533
stack backtrace:
#0 0xffff0000002eee98 at witness_debugger+0x64
#1 0xffff00000026ad88 at lockmgr_lock_fast_path+0x1b4
#2 0xffff000000590634 at VOP_LOCK1_APV+0xcc
#3 0xffff00000035cf3c at _vn_lock+0x6c
#4 0xffff00000034e98c at vget+0x78
#5 0xffff00000017d6a8 at devfs_allocv+0xdc
#6 0xffff00000017d1e0 at devfs_root+0x44
#7 0xffff000000345d2c at vfs_donmount+0x102c
#8 0xffff000000344ccc at sys_nmount+0x68
#9 0xffff000000573404 at do_el0_sync+0x8c8
#10 0xffff00000055c9f4 at handle_el0_sync+0x74
panic: vm_fault: fault on nofault entry, addr: ffff0000999ee000
cpuid = 18
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
         pc = 0xffff00000055ae28  lr = 0xffff00000005eb10
         sp = 0xffff00061d8dae40  fp = 0xffff00061d8db050

db_trace_self_wrapper() at vpanic+0x170
         pc = 0xffff00000005eb10  lr = 0xffff00000029346c
         sp = 0xffff00061d8db060  fp = 0xffff00061d8db0e0

vpanic() at panic+0x48
         pc = 0xffff00000029346c  lr = 0xffff0000002934f8
         sp = 0xffff00061d8db0f0  fp = 0xffff00061d8db170

panic() at vm_fault_hold+0x1ab0
         pc = 0xffff0000002934f8  lr = 0xffff00000052f1dc
         sp = 0xffff00061d8db180  fp = 0xffff00061d8db2d0

vm_fault_hold() at vm_fault+0x70
         pc = 0xffff00000052f1dc  lr = 0xffff00000052d6dc
         sp = 0xffff00061d8db2e0  fp = 0xffff00061d8db310

vm_fault() at data_abort+0xd8
         pc = 0xffff00000052d6dc  lr = 0xffff0000005729dc
         sp = 0xffff00061d8db320  fp = 0xffff00061d8db3d0

data_abort() at handle_el1h_sync+0x74
         pc = 0xffff0000005729dc  lr = 0xffff00000055c874
         sp = 0xffff00061d8db3e0  fp = 0xffff00061d8db4f0

handle_el1h_sync() at vnet_epair_init+0x2c
         pc = 0xffff00000055c874  lr = 0xffff00005996674c
         sp = 0xffff00061d8db500  fp = 0xffff00061d8db580

vnet_epair_init() at vnet_register_sysinit+0x100
         pc = 0xffff00005996674c  lr = 0xffff00000039e000
         sp = 0xffff00061d8db590  fp = 0xffff00061d8db5b0

vnet_register_sysinit() at linker_load_module+0xaac
         pc = 0xffff00000039e000  lr = 0xffff000000266a68
         sp = 0xffff00061d8db5c0  fp = 0xffff00061d8db8e0

linker_load_module() at kern_kldload+0xec
         pc = 0xffff000000266a68  lr = 0xffff000000268120
         sp = 0xffff00061d8db8f0  fp = 0xffff00061d8db920

kern_kldload() at sys_kldload+0x64
         pc = 0xffff000000268120  lr = 0xffff000000268278
         sp = 0xffff00061d8db930  fp = 0xffff00061d8db950

sys_kldload() at do_el0_sync+0x8c8
         pc = 0xffff000000268278  lr = 0xffff000000573404
         sp = 0xffff00061d8db960  fp = 0xffff00061d8dba80

do_el0_sync() at handle_el0_sync+0x74
         pc = 0xffff000000573404  lr = 0xffff00000055c9f4
         sp = 0xffff00061d8dba90  fp = 0xffff00061d8dbba0

handle_el0_sync() at 0x21278
         pc = 0xffff00000055c9f4  lr = 0x0000000000021278
         sp = 0xffff00061d8dbbb0  fp = 0x0000ffffffffe2d0

KDB: enter: panic
[ thread pid 1053 tid 101161 ]
Stopped at      kdb_enter+0x40: undefined       d4200000

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