System panic crash snippet:
PANIC: "BUG: unable to handle kernel NULL pointer dereference at 0000000000000520"
PID: 3866763
COMMAND: "vx_naio_worker"
TASK: ffff925cea27df00 [THREAD_INFO: ffff925cea27df00]
CPU: 2
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 3866763 TASK: ffff925cea27df00 CPU: 2 COMMAND: "vx_naio_worker"
#0 [ffffa550ac3bf438] machine_kexec at ffffffffbc46156e
#1 [ffffa550ac3bf490] __crash_kexec at ffffffffbc58f9ed
#2 [ffffa550ac3bf558] crash_kexec at ffffffffbc5908dd
#3 [ffffa550ac3bf570] oops_end at ffffffffbc42434d
#4 [ffffa550ac3bf590] no_context at ffffffffbc4725cf
#5 [ffffa550ac3bf5e8] __bad_area_nosemaphore at ffffffffbc47292c
#6 [ffffa550ac3bf630] do_page_fault at ffffffffbc473207
#7 [ffffa550ac3bf660] page_fault at ffffffffbce010fe
[exception RIP: vx_bio_associate_blkg+56]
RIP: ffffffffc0f456c8 RSP: ffffa550ac3bf710 RFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff925db096a100 RCX: 0000000000000000
RDX: ffff925cea27df00 RSI: 0000000000000000 RDI: ffff925db096a100
RBP: ffffa550ac3bf900 R8: ffff925db096a100 R9: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff925735a2f570
R13: ffff925dae67d680 R14: ffff925735a2f420 R15: ffff925735a2f400
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
#8 [ffffa550ac3bf718] vx_dio_physio at ffffffffc0f913a3 [vxfs]
#9 [ffffa550ac3bf910] vx_dio_rdwri at ffffffffc0e21a0a [vxfs]
#10 [ffffa550ac3bfb50] vx_dio_read at ffffffffc0f6acf6 [vxfs]
#11 [ffffa550ac3bfc18] vx_read_common_noinline at ffffffffc0f6c07e [vxfs]
#12 [ffffa550ac3bfce0] vx_read1 at ffffffffc0f6c96b [vxfs]
#13 [ffffa550ac3bfd88] vx_vop_read at ffffffffc0f4cce2 [vxfs]
#14 [ffffa550ac3bfdd8] vx_naio_do_work at ffffffffc0f240bb [vxfs]
#15 [ffffa550ac3bfec0] vx_naio_worker at ffffffffc0f249c3 [vxfs]
#16 [ffffa550ac3bfef8] vx_kthread_init at ffffffffc0f37192 [vxfs]
#17 [ffffa550ac3bff10] kthread at ffffffffbc5043d6
#18 [ffffa550ac3bff50] ret_from_fork at ffffffffbce00255
Following Linux 4.13.16 kernel changes, Volume Manager code ends up with an incorrect device inode reference count on its devices and can make VxFS panic when accessing the Volume Manager block_device.
Issue is addressed in Volume Manager hot-fix 7.4.2.2606 - please refer to Veritas Technical Support for the fix.