qemu-system: NULL pointer dereference

[discostur]

Hi,

we are running a SmartOS host with some KVM machines on it. Today we encountered the following kernel bug:

BAD TRAP: type=e (#pf Page fault) rp=fffffb040f3cde70 addr=0 occurred in module "<unknown>" due to a NULL pointer dereference
#012
qemu-system-x86_:
#pf Page fault
Bad kernel fault at addr=0x0
pid=822676, pc=0x0, sp=0xfffffb040f3cdf68, eflags=0x10202
cr0: 80050033<pg,wp,ne,et,mp,pe>  cr4: 3626f8<smap,smep,osxsav,pcide,vmxe,xmme,fxsr,pge,mce,pae,pse,de>
cr2: 0
cr3: 3f91457000
cr8: 0
#011rdi: fffffb04121c30d0 rsi:            1906a rdx:         e9ae2300
#011rcx:               1e  r8: fffffdc46c414194  r9: fffffdc46c414180
#011rax:                0 rbx:                1 rbp: fffffb040f3cdf80
#011r10: fffffdca66a1f500 r11: 7fffffffffffffff r12:               1e
#011r13:                0 r14:                0 r15:                0
#011fsb: fffff9ffef05aa40 gsb: fffffdc3df0bb000  ds:               38
#011 es:               38  fs:                0  gs:                0
#011trp:                e err:               10 rip:                0
#011 cs:               30 rfl:            10202 rsp: fffffb040f3cdf68
#011 ss:               38

fffffb040f3cdd60 unix:real_mode_stop_cpu_stage2_end+bcbc ()
fffffb040f3cde60 unix:trap+15d2 ()
fffffb040f3cde70 unix:cmntrap+e6 ()
fffffb040f3cdf80 0 ()
fffffb040f3cdfd0 apix:apix_dispatch_by_vector+8c ()
fffffb040f3cdff0 apix:apix_dispatch_hilevel+15 ()
ffffb041445a2e0 unix:switch_sp_and_call+13 ()
fffffb041445a340 apix:apix_do_interrupt+119 ()
fffffb041445a350 unix:cmnint+ba ()
fffffb041445a460 kvm:vcpu_enter_guest+3e7 ()
fffffb041445a4a0 kvm:__vcpu_run+9b ()
fffffb041445a4e0 kvm:kvm_arch_vcpu_ioctl_run+114 ()
fffffb041445acc0 kvm:kvm_ioctl+466 ()
fffffb041445ad00 genunix:cdev_ioctl+39 ()
fffffb041445ad50 specfs:spec_ioctl+60 ()
fffffb041445ade0 genunix:fop_ioctl+55 ()
fffffb041445af00 genunix:ioctl+9b ()
fffffb041445af10 unix:brand_sys_syscall+21a ()

Is there any chance this will get fixed?

We are running an older build of SmartOS back from 2018 ... maybe it got fixed in the meantime?

Thanks
Greets
Kilian