Error Message

Assessment of the crash dump showed the following:

 PANIC: "BUG: unable to handle kernel NULL pointer dereference at 0000000000000008"
         PID: 7415
     COMMAND: "llt_ioship_rsnd"
        TASK: ffff8fadef59d280  [THREAD_INFO: ffff8fb2e630c000]
         CPU: 2
       STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 7415   TASK: ffff8fadef59d280  CPU: 2   COMMAND: "llt_ioship_rsnd"
 #0 [ffff8fb2e630fa90] machine_kexec at ffffffff9c469504
 #1 [ffff8fb2e630faf0] __crash_kexec at ffffffff9c529d32
 #2 [ffff8fb2e630fbc0] crash_kexec at ffffffff9c529e28
 #3 [ffff8fb2e630fbd8] oops_end at ffffffff9cbbc818
 #4 [ffff8fb2e630fc00] no_context at ffffffff9c47970c
 #5 [ffff8fb2e630fc50] __bad_area_nosemaphore at ffffffff9c4799ea
 #6 [ffff8fb2e630fca0] bad_area_nosemaphore at ffffffff9c479b14
 #7 [ffff8fb2e630fcb0] __do_page_fault at ffffffff9cbbf8d0
 #8 [ffff8fb2e630fd20] do_page_fault at ffffffff9cbbfb05
 #9 [ffff8fb2e630fd50] page_fault at ffffffff9cbbb7b8
    [exception RIP: vx_ioship_change_gen+108]
    RIP: ffffffffc137c05c  RSP: ffff8fb2e630fe08  RFLAGS: 00010282
    RAX: ffff8fb17553db80  RBX: ffff8fb2b9dc1600  RCX: 0000000000000b5e
    RDX: 0000000000000000  RSI: 00000000000002a6  RDI: ffff8fb2b9dc1600
    RBP: ffff8fb2e630fe10   R8: ffff8fb2e630c000   R9: 0000000000000001
    R10: 0000000000000001  R11: 0000000000000000  R12: ffff8fb2b9dc1708
    R13: ffff8fb33c5eb800  R14: ffff8fb33c5eb800  R15: 0000000000000001
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
#10 [ffff8fb2e630fe18] vx_ioship_resend_internal at ffffffffc137eeae [llt]
#11 [ffff8fb2e630fe40] vx_ioship_node_resend at ffffffffc137ef2b [llt]
#12 [ffff8fb2e630fe68] vx_ioship_process_resend at ffffffffc137ffbf [llt]

The crash was triggered due to packet duplication in the User Datagram Protocol (UDP) and inability for VCS's UDP multi-port feature to deal with it. The feature was introduced in Infoscale 7.3.1 and is only applicable to the Linux operating system 

There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. While this issue may be resolved in a future major revision of the software at a later time, it is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.

Fix is available via llt-rhel7_x86_64-HotFix-7.4.2.3402. Please refer this article to Veritas Technical Support to obtain it.

A fix will also be part of future 8.0 and 8.0.2 releases.