README VERSION : 1.0 README Creation Date : 2011-09-07 Patch-ID : 143271-07 Patch Name : VRTSodm 5.1SP1RP2 BASE PACKAGE NAME : VRTSodm BASE PACKAGE VERSION : 5.1 Obsolete Patches : NONE Superseded Patches : 143271-06 Required Patches : 143271-05 Incompatible Patches : NONE Supported PADV : sol10_sparc (P-Platform , A-Architecture , D-Distribution , V-Version) Patch Category : PANIC Reboot Required : NO FIXED INCIDENTS: ---------------- Patch Id::143271-07 * Incident no::2407896 Tracking ID ::2407895 Symptom::System panic in atomic_add_32_nv with the following stack atomic_add_32_nv odm:odmdirlook_zone odm:odmdirlook - frame recycled odm:odmlookup genunix:fop_lookup lofs:lo_lookup genunix:fop_lookup genunix:lookuppnvp genunix:lookuppnat genunix:lookupnameat genunix:vn_openat genunix:copen Description::The odm device should be mounted from local zones by executing "mount -F odm /dev/odm /dev/odm", and a corresponding mount entry will be generated for each local zone for odm lookup, read and write etc. However, if user mounting odm device from global zone, for example, "mount -F lofs /dev/odm /export/home/myzone/root/dev/odm", the odm mount entry for this zone will not be created, which results in panic when accessing the mount entry in kernel. Resolution::Mount the odm device from local zone. Additionally, add code to avoid panic for invalid mount.