IZ53534: pthread key destructors may be re-entered if they call pthread_s elf or mutex functions

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• Another team using the SSM pthread library on Windows is seeing
  pthread key destructors called twice when they should only occur
  once. This results in data corruption and potential crashes.
  While we do not think this bug can affect SSM 4.0, the problem
  and it's solution is still being documented here.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  No SSM users are affected at the moment.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Another product using the SSM pthread library on Windows is
  seeing pthread key destructors called twice when they should
  only occur once. This results in data corruption and potential
  crashes.
  
  While we do not think this bug can affect SSM 4.0, the problem
  and it's solution is still being documented here because the
  library is maintained and included in SSM 4.0.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 8 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• Set thread-specific key value to NULL before calling the
  destructor. That's what the specification requires, and it also
  stops the destructor from being called twice. If for some reason
  the destructor re-initializes the key value then destructor
  calls are made repeatedly (up to four attempts) as per the
  pthread specification.
  http://www.opengroup.org/onlinepubs/009695399/functions/pthread_
  key_create.html
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0008
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSN

     UP