Patch Name: PHKL_21680 Patch Description: s700_800 11.00 Fix panic on deadlock: NULL thread ptr Creation Date: 00/05/11 Post Date: 00/05/22 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: N/A Filesets: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_21680: PANIC Category Tags: defect_repair general_release critical panic Path Name: /hp-ux_patches/s700_800/11.X/PHKL_21680 Symptoms: PHKL_21680: ( SR: 8606134000 CR: JAGad03140 ) When using lockf(2) or fcntl(2) system calls to lock a file or regions of a file, the system may panic with "deadlock: NULL thread ptr associated with filelock". The stack trace has the following pattern: 0) panic+0x14 1) deadlock+0x118 2) locked+0x1f0 3) local_lockctl+0xf4 4) fcntl+0x2e4 5) syscall+0x480 6) $syscallrtn+0x0 Defect Description: PHKL_21680: ( SR: 8606134000 CR: JAGad03140 ) In the deadlock detection routine, if the kernel finds that a thread which owns a file lock (locking a file or records by calling lockf(2) or fcntl(2)) has been terminated without releasing the lock, it panics. The system should not panic in this situation as it will not cause a problem or deadlock; the lock can be released by another thread, or it will be released when the process exits. Resolution: The panic condition has been changed. The system panics only if deadlock() can not find the thread which locked the file, and the process of the thread does not exist or is in zombie state. The panic message has been changed to: "deadlock: terminated process associated with filelock". SR: 8606134000 Patch Files: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libhp-ux.a(vfs_lockf.o) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(vfs_lockf.o) what(1) Output: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libhp-ux.a(vfs_lockf.o): vfs_lockf.c $Date: 2000/05/10 09:36:06 $Revision: r1 1ros/6 PATCH_11.00 (PHKL_21680) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(vfs_lockf.o): vfs_lockf.c $Date: 2000/05/10 09:36:06 $Revision: r1 1ros/6 PATCH_11.00 (PHKL_21680) cksum(1) Output: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: 786787523 17436 /usr/conf/lib/libhp-ux.a(vfs_lockf.o) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 1908067956 40208 /usr/conf/lib/libhp-ux.a(vfs_lockf.o) Patch Conflicts: None Patch Dependencies: s700: 11.00: PHKL_18543 s800: 11.00: PHKL_18543 Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: None Patch Package Size: 90 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_21680 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHKL_21680.depot By default swinstall will archive the original software in /var/adm/sw/save/PHKL_21680. If you do not wish to retain a copy of the original software, use the patch_save_files option: swinstall -x autoreboot=true -x patch_match_target=true \ -x patch_save_files=false -s /tmp/PHKL_21680.depot WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHKL_21680.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHKL_21680.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_21680.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: This patch depends on base patch PHKL_18543. For successful installation please insure that PHKL_18543 is already installed, or that PHKL_18543 is included in the same depot with this patch and PHKL_18543 is selected for installation.