README VERSION		: 1.1
README CREATION DATE	: 2012-09-20
PATCH ID 		: 5.1.113.0 
PATCH NAME		: VRTSamf 5.1 SP1RP3
BASE PACKAGE NAME	: Veritas Asynchronous Monitoring Framework by Symantec
BASE PACKAGE VERSION	: VRTSamf 5.1SP1
SUPERSEDED PATCHES	: NONE
REQUIRED PATCHES	: NONE
INCOMPATIBLE PATCHES	: NONE
SUPPORTED PADV		: aix53,aix61,aix71
(P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION)
PATCH CATEGORY		:  PANIC
PATCH CRITICALITY	: OPTIONAL
HAS KERNEL COMPONENT	: YES
ID			: NONE
REBOOT REQUIRED		: NO

PATCH INSTALLATION INSTRUCTIONS:
--------------------------------


Please refer the release notes for installation instructions

PATCH UNINSTALLATION INSTRUCTIONS:
----------------------------------
Please refer the release notes for un-installation instructions.

SPECIAL INSTRUCTIONS:
----------------------
NONE

SUMMARY OF FIXED ISSUES:
-----------------------------------------
2636875 (2636874)  AMF calls VxFS API with spinlock held. 


SUMMARY OF KNOWN ISSUES:
-----------------------------------------


KNOWN ISSUES : 
--------------


FIXED INCIDENTS: 


 PATCH ID:5.1.113.0

 * INCIDENT NO:2636875	 TRACKING ID:2636874

SYMPTOM: The system panics when monitoring Veritas File System (VxFS) resources. 

DESCRIPTION: Asynchronous Monitoring Framework (AMF) calls the VxFS API when
holding a spinlock. 

RESOLUTION: Symantec has fixed the code. Now the VxFS API is called outside of a
spinlock. 

INCIDENTS FROM OLD PATCHES:
---------------------------
Patch Id::5.1.112.0

 * Incident no::2301731  Tracking ID ::2301709

 Symptom::Kernel panics when you unconfigure the AMF driver.

 Description::There was a race condition between a system call and the AMF driver
unconfiguration which caused this issue.

 Resolution::Symantec modified the code to address this race condition.

 * Incident no::2403851  Tracking ID ::2403846

 Symptom::System cannot unload the AMF driver.

 Description::An error in the code prevented the AMF module from being unloaded
though the module was not being used.

 Resolution::Symantec has modified the code. AMF module can be unloaded when it
is not in use.

 * Incident no::2406748  Tracking ID ::2406746

 Symptom::Offline registration for a process with AMF succeeds even when the
process is running.

 Description::When AMF processes the offline registration request, stale data
from earlier cycles causes an online process to be reported as offline.

 Resolution::Symantec had modified the code to remove the stale data. The
correct status is passed on to registration requests.

 * Incident no::2407653  Tracking ID ::2407652

 Symptom::The module reference count on the filesystem registered with AMF for
mount offline monitoring or mount online monitoring is not released when you
forcefully unconfigure AMF using the "amfconfig -Uof" command.

 Description::When forcefully unconfiguring AMF, it was not releasing its
reference from the filesystem modules. This caused extra reference counts on
these modules to remain even after AMF driver was unloaded.

 Resolution::Symantec modified the code for proper reference counting on these
filesystem modules during forceful unconfiguration of AMF.


* Incident no::2518226   Tracking ID ::2518209

 Symptom::On AIX systems, kernel panics when it mounts a NFS file system.

 Description::The AMF driver was not handling the NFS mount properly, causing a
NULL pointer dereference.

 Resolution::Symantec modified the code to handle NFS mounts correctly.