Error Message

[  480.571482] BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
[  480.580203] IP: d_path+0x24/0x130
[  480.583919] PGD 800000101436b067 P4D 800000101436b067 PUD ff89b8067 PMD 0
[  480.591698] Oops: 0000 [#1] SMP PTI
[  480.595607] CPU: 1 PID: 15130 Comm: MountAgent Tainted: P           OE      4.12.14-122.231-default #1 SLE12-SP5
[  480.606904] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/21/2019
[  480.616077] task: ffff974f13601100 task.stack: ffffba6a72164000
[  480.622660] RIP: 0010:d_path+0x24/0x130
[  480.626944] RSP: 0018:ffffba6a72167750 EFLAGS: 00010286
[  480.632759] RAX: ffff974ee5c53000 RBX: ffffba6a721677b8 RCX: ffff9740b7d62ea8
[  480.640674] RDX: 0000000000001000 RSI: ffff974ee5c52000 RDI: 0000000000000000
[  480.648588] RBP: ffffba6a72167778 R08: 3673612f6473752f R09: 0000000000ede73e
[  480.656505] R10: 0000000000000000 R11: 0000000000000000 R12: ffff974f0e556300
[  480.664418] R13: ffffffffc12d11a0 R14: ffff974ee5c52000 R15: 0000000000000000
[  480.672333] FS:  00007ff7c524f700(0000) GS:ffff974f3f840000(0000) knlGS:0000000000000000
[  480.681309] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  480.687692] CR2: 0000000000000060 CR3: 0000001008ffa003 CR4: 00000000001606e0
[  480.695607] Call Trace:
[  480.698369]  ? mnt_list_next.isra.25+0x1b/0x60
[  480.703330]  amf_plat_fs_verify+0x10c/0x270 [amf]
[  480.708570]  ? select_idle_sibling+0x28/0x430
[  480.713535]  ? _copy_from_user+0x33/0x70
[  480.717916]  ? amf_copyin+0x13/0x30 [amf]
[  480.722390]  ? amf_ev_fs_attr_copyin+0x284/0x380 [amf]
[  480.728107]  ? update_curr+0x77/0x1a0
[  480.732200]  ? amf_ev_fsoff_verify+0x14/0x50 [amf]
[  480.737534]  ? amf_event_reg+0x348/0xc00 [amf]
[  480.742488]  ? amfioctl+0x105a/0x1d75 [amf]
[  480.747152]  ? hrtimer_try_to_cancel+0x15/0x100
[  480.752201]  ? schedule_hrtimeout_range_clock+0x96/0x120
[  480.758108]  ? hrtimer_init+0x180/0x180
[  480.762392]  ? sock_poll+0x75/0x90
[  480.766197]  ? do_select+0x6a5/0x760
[  480.770196]  ? get_page_from_freelist+0x4bf/0x1340
[  480.775531]  ? ____cache_alloc.part.64+0x1b0/0x29d
[  480.780866]  ? kmem_cache_alloc+0xe4/0x1d0
[  480.785440]  ? __wake_up_common_lock+0x77/0x90
[  480.790392]  ? __d_lookup_done+0x70/0xd0
[  480.794771]  ? lookup_fast+0x194/0x300
[  480.798965]  ? amf_close+0x10/0x10 [amf]
[  480.803342]  ? chrdev_open+0xab/0x190
[  480.807432]  ? dput+0xe0/0x1d0
[  480.810853]  ? terminate_walk+0x5b/0xc0
[  480.815133]  ? path_openat+0x67c/0x1340
[  480.819419]  ? tlb_flush_mmu_free+0x31/0x50
[  480.824085]  ? ptep_set_access_flags+0x42/0x70
[  480.829037]  ? do_filp_open+0x92/0xe0
[  480.833129]  ? audit_filter_rules.isra.14+0x554/0x1020
[  480.838927]  ? amf_ioctl+0x79/0x190 [amf]
[  480.843401]  ? do_vfs_ioctl+0x99/0x5f0
[  480.847588]  ? __audit_syscall_entry+0xb6/0x110
[  480.852640]  ? syscall_trace_enter+0x1b4/0x2a0
[  480.857591]  ? SyS_ioctl+0x78/0x90
[  480.861405]  ? do_syscall_64+0x74/0x160
[  480.865687]  ? entry_SYSCALL_64_after_hwframe+0x7d/0xe7
 

This is currently under investigation.

This issue is presently under investigation by our Engineering Team. Depending on the results of this investigation, it may be addressed through a patch or hotfix in current or future software releases. However, this specific issue is not currently scheduled for inclusion in any upcoming release. If this issue has a significant business impact on your continued use of the product, please contact your Sales representative or the Sales team to discuss your concerns.
 
Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

The workaround is to disable IMF for the Mount and CFSMount agents on each node in the cluster. 

If planning to install this kernel, then disable IMF for the Mount and CFSMount agents on each node in the cluster prior to installing the kernel. If the kernel is already installed and a panic is encountered, disable IMF for the Mount and CFSMount agents on each node in the cluster:

To disable IMF for the Mount and CFSMount agents, run the following commands on each node in the cluster:

# /opt/VRTSvcs/bin/haimfconfig/haimfconfig -display

#Agent          STATUS
Apache          ENABLED
Application     ENABLED
CFSMount        ENABLED
CFSfsckd        ENABLED
CSSD            ENABLED
CVMVxconfigd    ENABLED
Db2udb          ENABLED
DiskGroup       ENABLED
Mount           ENABLED
Netlsnr         ENABLED
Oracle          ENABLED
Process         ENABLED
SambaShare      ENABLED
Sybase          ENABLED
SybaseBk        ENABLED

# /opt/VRTSvcs/bin/haimfconfig -disable -agent Mount
VCS INFO V-16-52-53 Log created at '/var/VRTSvcs/log/haimfconfig_A.log'.
VCS WARNING V-16-52-59 This will change configuration files. Do you want to continue (yes/no)?: [yes] yes
IMF is successfully disabled for 'Mount' agent

# /opt/VRTSvcs/bin/haimfconfig -disable -agent CFSMount
VCS INFO V-16-52-53 Log created at '/var/VRTSvcs/log/haimfconfig_A.log'.
VCS WARNING V-16-52-59 This will change configuration files. Do you want to continue (yes/no)?: [yes] yes
IMF is successfully disabled for 'CFSMount' agent

# /opt/VRTSvcs/bin/haimfconfig/haimfconfig -display
#Agent          STATUS
Apache          ENABLED
Application     ENABLED
CFSMount        DISABLED
CFSfsckd        ENABLED
CSSD            ENABLED
CVMVxconfigd    ENABLED
Db2udb          ENABLED
DiskGroup       ENABLED
Mount           DISABLED
Netlsnr         ENABLED
Oracle          ENABLED
Process         ENABLED
SambaShare      ENABLED
Sybase          ENABLED
SybaseBk        ENABLED
 

The fix for this issue has been included in a hotfix for InfoScale 7.4.2 and InfoScale 7.4.2 update 8 (infoscale-sles12_x86_64-Patch-7.4.2.5600) included in the forthcoming InfoScale 8.0update4 patches for sles12. The recommendation is to implement the workaround and/or install the InfoScale 7.4.2update8 and InfoScale 8.0update4 patches. Should the hotfix be required, please contact Infoscale Technical Support.  These panics are specific to the sles12sp5 minor release and so won't occur with InfoScale 8.0.2/sles15. 

If IMF (Intelligent Monitoring Framework) is used for monitoring Mount or CFSMount resources in a VCS 7.4.2 or VCS 8.0 cluster with sles12sp5 (kernel 4.12.14-122.231 and above), a panic may be observed on the nodes in the cluster.

JIRA: STESC-9310