IBM Platform Symphony 7.1 Interim Fix 366258 Readme File
Abstract
This fix resolves the VEMKD
core dumping if there is a long value for the client name attribute in vem_register().
Description
The length of the client name attribute
used in the vem_register() call to VEMKD causes the system
to core dump. If the client name value is greater than 60, it overflows the
buffer and causes memory corruption for VEMKD.
With this fix, the limitation of 60 characters
has been extended to 256. Additionally, if the client
name is greater than 256 characters, an error displays, rather than causing a core
dump.
This interim fix applies
only to the following platform:
Linux2.6-glibc2.3-x86_64
Readme file
for: IBM® Platform
Symphony
Product/Component Release: 7.1 Fix Pack 1
Update Name: Interim Fix 366258
Fix ID: sym7.1-build366258
Publication date: 16
October 2015
Last modified date: 16
October 2015
Contents:
1. List of fixes
2. Download location
3. Products or components affected
4. Installation and configuration
5. List of files
6. Copyright and trademark information
1. List of fixes
APAR#P101400
2. Download location
Download Interim Fix 366258 from the following location: http://www.ibm.com/eserver/support/fixes/.
3. Products or components affected
Product/Component
Name, Platform, Fix ID:
Platform Symphony/VEMKD and libvem.so
Linux 64-bit, sym7.1-build366258
4. Installation and configuration
4.1 Before installation
1. Shutdown the cluster.
Log on to the host as
the cluster administrator and run:
> soamcontrol app disable all
> egosh service stop all
> egosh ego shutdown all
2. Backup the affected files.
Log on to all hosts in
the cluster, and back up the following files that will be
replaced by this fix:
>$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/etc/vemkd
>$EGO_TOP/soam/7.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
>$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
4.2
Installation steps
Log on to
all hosts in the cluster, and replace the old files with the downloaded
package:
> tar zxvf sym7.1-build366258_lnx26-lib23-x64.tar.gz
-C $EGO_TOP
4.3 After installation
1. Start the cluster.
Log on to the master
host as the cluster administrator and run:
> egosh ego start all
> soamcontrol app enable appname
4.4 Uninstallation
1. Shut
down the cluster.
Log on to the master host
as the cluster administrator and run:
> soamcontrol app disable all
> egosh service stop all
> egosh ego shutdown all
2. Restore the backup
file.
Log on to all hosts and
restore the backed up files:
>$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/etc/vemkd
>$EGO_TOP/soam/7.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
>$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
3. Start the cluster.
Log on to the master
host as the cluster administrator and run:
> egosh ego start all
> soamcontrol app enable appname
5. List of files
$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/etc/vemkd
$EGO_TOP/3.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
$EGO_TOP/soam/7.1/linux2.6-glibc2.3-x86_64/lib/libvem.so
6. Copyright and trademark information
© Copyright IBM Corporation 2015
U.S. Government Users Restricted Rights - Use,
duplication or disclosure restricted by GSA ADP Schedule Contract with IBM
Corp.
IBM®, the IBM logo and ibm.com® are trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide. Other
product and service names might be trademarks of IBM or other companies. A
current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.