Error Message

CAT(vmcore.10/11V)> panic
panic on CPU 2
panic string: kernel heap corruption detected
==== panic kernel thread: 0x2a1072e7b00 PID: 0 on CPU: 2 ====
cmd: sched(vxio:voliod_loop)
.
.

void unix:panicsys+0x40((const char *)0x1085ccc9, (va_list)0x2a1072e74a8, (struct regs *)0x20672870, (int)1, 0x1606, , , , , , , , 0x1085ccc9, 0x2a1072e74a8)
unix:vpanic_common+0x78(0x1085ccc9, 0x2a1072e74a8, 0, 0x50, 0xc8, 0x2a1072e7288)
void unix:panic+0x1c((const char *)0x1085ccc9, 0x1085cc00, 0xfc, 0x4000b02d286, 0x1085ec00, 0x1085ec00, ...)
void genunix:kmem_error+0x5f0((kmem_errid_t), (kmem_cache_t *)0x1085cc00?, (void *))
genunix:kmem_free((void *)0xa007747b090, (size_t)0x50) - frame recycled
int vxio:vol_page_offsetlist_sort+0x164((voff_t *)0xa007666d8d8, (vx_u64_t)6, (vx_u32_t)0, (vx_u64_t *)0)
int vxio:volpage_freelist+0x278((vol_pagesioreq_t *)0xa0076f24800, (unsigned long), (voff_t *)0xa007666d2a8, (struct volkcontext *)0x2a1072e78b0)
int vxio:vol_cvol_shadow2_done+0xb8((struct volsio *)0xa0042b3f040, (struct volkcontext *)0x2a1072e78b0)
void vxio:voliod_iohandle+0x74((struct volsio *), (int)0, (struct volkcontext *)0x2a1072e78b0)
void vxio:voliod_loop+0xfc((void *)0)
unix:thread_start+4()
– end of kernel thread's stack –

 

 

Veritas code was incorrectly overwriting the boundary of the allocated space.

Due to a bug in sorting the large offset, the Veritas code overwrote the boundary of the allocated memory and caused the panic.

The related Veritas function was incorrectly declaring a 64-bit value as a 32-bit value.
After changing from a 32-bit data sort value to 64-bit sort value, we now retrieve the expected results.

 

Veritas engineering have released Veritas Volume Manger (VxVM) Private Hot-fix "vm-sol11_sparc-HotFix-7.4.2.3201".

Please contact Veritas Technical Support to obtain the VxVM Private Hot-fix.

PATCH NAME
----------
Veritas Volume Manager 7.4.2 Hot Fix 3201

OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 11 SPARC

PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxvm

BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Enterprise 7.4.2
   * InfoScale Foundation 7.4.2
   * InfoScale Storage 7.4.2

SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.4.2.3201
* 4090830 (4090826) system panic at vol_page_offsetlist_sort

DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 7.4.2.3201

* 4090830 (Tracking ID: 4090826)

SYMPTOM:
system panic at vol_page_offsetlist_sort with below stack:

vpanic()
kmem_error+0x5f0()
vol_page_offsetlist_sort+0x164()
volpage_freelist+0x278()
vol_cvol_shadow2_done+0xb8()

DESCRIPTION:
Due to a bug in sorting the large offset, the code overwrote the boundary of the allocated memory and caused the panic.

RESOLUTION:
The code change has been made to sort the large offset correctly.
 

Solaris 11.4 LDOM environments are experiencing sudden application crashes caused by a Veritas triggered panic. System panic triggered by vol_page_offsetlist_sort with below stack: vpanic()
kmem_error+0x5f0()
vol_page_offsetlist_sort+0x164()
volpage_freelist+0x278()
vol_cvol_shadow2_done+0xb8() Kernel Memory Allocator:

redzone violation: write past end of buffer
buffer=a007747b090 bufctl=4056286c200 cache: kmem_alloc_80
previous transaction on buffer a007747b090:

A special pattern enables the allocator (and a programmer debugger) to determine whether the boundaries of a buffer have been violated.

The special pattern is known as a redzone indicator.