Error Message

From the messages dump from the core, null pointer deference panic ends in vx_bio_associate_blkg call:

[2455264.130843] BUG: unable to handle kernel NULL pointer dereference at 0000000000000520
[2455264.149808] CPU: 22 PID: 478546 Comm: mh_driver.pl Kdump: loaded Tainted: P           OE    --------- -  - 4.18.0-348.2.1.el8_5.x86_64 #1
[2455264.162428] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 01/23/2021
[2455264.171261] RIP: 0010:vx_bio_associate_blkg+0x44/0x90 [vxfs]
[2455264.177139] Code: 08 c3 48 89 3c 24 e8 8b 87 74 cb 48 8b 3c 24 48 85 c0 75 e2 65 48 8b 04 25 40 5c 01 00 48 8b 80 08 0d 00 00 eb d0 48 8b 47 08 <48> 8b 80 20 05 00 00
48 8b 90 78 04 00 00 48 8b 42 48 a8 03 75 1f
[2455264.196235] RSP: 0018:ffffa916f5646cb0 EFLAGS: 00010246
[2455264.201674] RAX: 0000000000000000 RBX: ffff953180613a00 RCX: 0000000000000000
[2455264.209040] RDX: ffff95615e93bd80 RSI: 0000000000000000 RDI: ffff953180613a00
[2455264.216407] RBP: ffffa916f5646ea0 R08: ffff953180613a00 R09: 0000000000000000
[2455264.223771] R10: 0000000000000001 R11: 0000000000000002 R12: ffff950a2c70c370
[2455264.231135] R13: ffff94ec83ee0000 R14: ffff950a2c70c220 R15: ffff950a2c70c200
[2455264.238500] FS:  00007fe7d3afd740(0000) GS:ffff95a23fb80000(0000) knlGS:0000000000000000
[2455264.246827] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[2455264.252790] CR2: 0000000000000520 CR3: 0000004c69ca8003 CR4: 00000000007706e0
[2455264.260154] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[2455264.267519] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[2455264.274894] PKRU: 55555554
[2455264.277796] Call Trace:
[2455264.280502]  vx_dio_physio+0x16a3/0x32a0 [vxfs]
[2455264.285284]  ? vx_iget+0x1235/0x14b0 [vxfs]
[2455264.289707]  ? vx_dio_rdwri+0x8fa/0x1350 [vxfs]
[2455264.294471]  ? vx_bmap_protected+0xad/0xe0 [vxfs]
[2455264.299417]  vx_dio_rdwri+0x8fa/0x1350 [vxfs]
[2455264.303990]  ? __schedule+0x2cc/0x700
[2455264.307893]  vx_dio_read+0x1b6/0x370 [vxfs]
[2455264.312320]  vx_read_common_noinline+0x6fe/0x9e0 [vxfs]
[2455264.317797]  vx_read1+0x60b/0xc20 [vxfs]
[2455264.321964]  ? vx_rwsleep_rec_lock+0x1b/0xe0 [vxfs]
[2455264.327091]  ? vx_recsmp_rangelock+0x14/0x30 [vxfs]
[2455264.332221]  ? vx_rwsleep_rec_unlock+0x1a/0xd0 [vxfs]
[2455264.337523]  vx_vop_read+0x82/0x130 [vxfs]
 

The panic gets triggered by mh_driver.pl. This is a VIOM perl script, which calls Volume Manager/Filesystem discovery routines. In turn, this leads to a known bug in call vx_bio_associate_blkg.

A fix is now available for this issue for Volume Manager 7.4.2.2606 .

Please contact Veritas Technical Support for this fix.