Patch Name: PHKL_16880

Patch Description: s700 10.20 a fix involving fcntl and mmap interactions

Creation Date: 98/11/13

Post Date:  98/12/02

Hardware Platforms - OS Releases:
	s700: 10.20

Products: N/A

Filesets:
	OS-Core.CORE-KRN

Automatic Reboot?: Yes

Status: General Superseded

Critical: No

Path Name: /hp-ux_patches/s700/10.X/PHKL_16880

Symptoms:
	PHKL_16880:
	It is possible for "munmap" to unexpectedly release the
	lock that is obtained from "fcntl".  The application may
	experience an unexpected behavior because of this.
	Therefore, this patch is to rectify this unexpected
	behavior.

Defect Description:
	PHKL_16880:
	To correct the problem, the associations between
	"memory mapped file" and the system-wide file table
	reference count is removed.  (i.e. The reference count
	is no longer stored in the system wide file table,
	however, the vnode reference counter still gets updated
	when "mmap" and "munmap".)

SR:
	1653277004

Patch Files:
	/usr/conf/lib/libhp-ux.a(vm_mmap.o)
	/usr/conf/lib/libhp-ux.a(vm_pregion.o)

what(1) Output:
	/usr/conf/lib/libhp-ux.a(vm_mmap.o):
		vm_mmap.c     $Date: 98/11/13 09:09:56 $ $Revision:
			1.17.98.20 $ PATCH_10.20 (PHKL_16880)
	/usr/conf/lib/libhp-ux.a(vm_pregion.o):
		vm_pregion.c  $Date: 98/11/09 12:45:48 $ $Revision:
			1.16.98.14 $ PATCH_10.20 (PHKL_16880)

cksum(1) Output:
	750178008 21276 /usr/conf/lib/libhp-ux.a(vm_mmap.o)
	1628516444 11928 /usr/conf/lib/libhp-ux.a(vm_pregion.o)

Patch Conflicts: None

Patch Dependencies:
	s700: 10.20: PHKL_16750

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches:
	PHKL_16881:
	s800: 10.20

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_16880

	5a. For a standalone system, run swinstall to install the
	    patch:

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHKL_16880.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_16880.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.

	By default swinstall will archive the original software in
	/var/adm/sw/patch/PHKL_16880.  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_16880.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_16880.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	This patch depends on base patch PHKL_16750 .
	For successful installation please insure that PHKL_16750
	is in the same depot with PHKL_16880, or PHKL_16750  is
	already installed.