Patch Name: PHKL_7299 Patch Description: s700 10.01 Fixes for shared-memory and memory-mapped file Creation Date: 96/04/18 Post Date: 96/04/19 Hardware Platforms - OS Releases: s700: 10.01 Products: N/A Filesets: OS-Core.CORE-KRN Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_7299: PANIC Path Name: /hp-ux_patches/s700/10.X/PHKL_7299 Symptoms: PHKL_7299: System panic with "Data page fault" in invalidate_protids() when using mprotect(2): trap type 15, pcsq.pcoq = 0.249f0c, isr.ior = 0.6c panic: (display==0xb800, flags==0x0) Data page fault panic+0x10 report_trap_or_int_and_panic+0x8c trap+0x72c invalidate_protids+0xbc hdl_changerange+0x1e0 hdl_mprotect+0x398 do_mprotect+0x140 foreach_pregion+0xe8 mprotect+0x78 syscall+0x1f4 This panic was mostly observed on systems running SAP R/3. PHKL_6118: This patch fixes a defect that causes a user process to hang while accessing shared memory. The process will experience an infinite series of protection faults that cannot be properly resolved. The process is therefore stuck executing the same load or store instruction and it will consume virtually all the CPU cycles on the machine. However, the system as a whole is not hung, so other process can still make progress. Defect Description: PHKL_7299: The code for processes Virtual Address Space duplication (used by fork) inserted pregions in the associated region lists before setting the VAS field va_proc. This opened a time window where invalidate_protids() could dereference a va_proc pointer before it was actually set. The system would then trap and panic with a data page fault. The defect would occur when using mprotect(2), and this panic was mostly observed on systems running SAP R/3. PHKL_6118: The defect occurs because of a bug in the exec system call. The bug is that exec does not properly clear protection id registers after a vfork. This causes the system to improperly generate protection faults that cannot be properly resolved so that the process can continue making forward progress. The defect only occurs after a vfork/exec sequence; the fork/exec sequence works okay. Note that in the 9.01 release, system(3C) uses fork, but in 10.01, it uses vfork. As a result, if you are porting code (that uses shared memory) from 9.01 to 10.01 and you see a hang, you could be experiencing this problem. SR: 1653166785 5003285163 Patch Files: /usr/conf/lib/libhp-ux.a(pm_procdup.o) /usr/conf/lib/libhp-ux.a(vm_vas.o) what(1) Output: /usr/conf/lib/libhp-ux.a(pm_procdup.o): pm_procdup.c $Date: 96/04/15 21:12:02 $ $Revision: 1.7.72.17 $ PATCH_10.01 (PHKL_7299) /usr/conf/lib/libhp-ux.a(vm_vas.o): vm_vas.c $Date: 96/04/15 21:15:57 $ $Revision: 1.13.72.25 $ PATCH_10.01 (PHKL_7299) cksum(1) Output: 726067273 5164 /usr/conf/lib/libhp-ux.a(pm_procdup.o) 918170043 10772 /usr/conf/lib/libhp-ux.a(vm_vas.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_6118 Equivalent Patches: PHKL_7300: s800: 10.01 PHKL_7301: s700: 10.10 PHKL_7302: s800: 10.10 Patch Package Size: 70 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHKL_7299 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_7299.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHKL_7299.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHKL_7299. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHKL_7299.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_7299.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None