System panic due to VxFS LRU list inconsistency after applying Infoscale 8.0.2 U6

Problem

System panic is observed after applying Infoscale 8.0.2 Update 6 on RHEL 8.x/9.x due to VxFS LRU list inconsistency

Error Message

The issue is seen both on Parallel Filesystem (CFS) as well as local/Failover VxFS Mount and the Panic String looks as below:

 #0 [ffffc13000bbfb58] machine_kexec at ffffffff9f26dde3
 #1 [ffffc13000bbfbb0] __crash_kexec at ffffffff9f3b9caa
 #2 [ffffc13000bbfc70] crash_kexec at ffffffff9f3babe1
 #3 [ffffc13000bbfc88] oops_end at ffffffff9f22c131
 #4 [ffffc13000bbfca8] do_trap at ffffffff9f228397
 #5 [ffffc13000bbfcf0] do_invalid_op at ffffffff9f2290d6
 #6 [ffffc13000bbfd10] invalid_op at ffffffff9fe00df4
    [exception RIP: __list_del_entry_valid.cold.1+32]
    RIP: ffffffff9f6f9308  RSP: ffffc13000bbfdc0  RFLAGS: 00010246
    RAX: 0000000000000054  RBX: ffff9ef89d99e220  RCX: 0000000000000000
    RDX: 0000000000000000  RSI: ffff9f0b60cde698  RDI: ffff9f0b60cde698
    RBP: ffff9ef96fa30fc0   R8: 0000000000000000   R9: c0000000ffff7fff
    R10: 0000000000000001  R11: ffffc13000bbfbe0  R12: 0000000000000029
    R13: ffff9f0e399714a8  R14: ffffffffc2d40df8  R15: ffffffffc2d40e08
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #7 [ffffc13000bbfdc0] vx_ddelete at ffffffffc2b48c3e [vxfs]
 #8 [ffffc13000bbfe00] dput at ffffffff9f589b30
 #9 [ffffc13000bbfe18] do_renameat2 at ffffffff9f5806d3
#10 [ffffc13000bbff28] do_renameat2 at ffffffff9f580335
#11 [ffffc13000bbff38] do_syscall_64 at ffffffff9f203cab
#12 [ffffc13000bbff50] entry_SYSCALL_64_after_hwframe at ffffffff9fe0012e

Cause

To improve parallel lookup performance, enhancements were made to the Least Recently Used (LRU) list logic. As part of this evolution, an unexpected behavior was observed in the VxFS rename operation.

In certain scenarios, specific memory lists may become misaligned due to lock interactions designed to manage list integrity. These conditions are isolated to internal list structures and do not result in any file system or data corruption.

The situation reflects a metadata-level irregularity, which remains fully non-impactful to user data.

Solution

A hotfix is now available for this issue in the current version of the product(s) mentioned. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue.. Please note that our company reserves the right to withdraw any fix from the targeted release if it fails quality assurance tests. Development plans are subject to change, and any actions you take based on this information, or your reliance on it, are at your own risk.

VXFS HotFix :

https://www.veritas.com/support/en_US/downloads/update.UPD680412  (RHEL 8)
https://www.veritas.com/support/en_US/downloads/update.UPD321672  (RHEL 9)
https://www.veritas.com/support/en_US/downloads/update.UPD725294  (SLES 15)

ODM HotFix :
https://www.veritas.com/support/en_US/downloads/update.UPD549595  (RHEL 8)
https://www.veritas.com/support/en_US/downloads/update.UPD929313  (RHEL 9)
https://www.veritas.com/support/en_US/downloads/update.UPD250348  (SLES 15)