A fix is available
APAR status
Closed as program error.
Error description
When asynchronous events are generated and delivered, sometimes it could potentially cause the dapli_thread to hang (trying to lock a word that is not valid). This could severely affect the future processing of connections etc.
Local fix
Problem summary
When asynchronous events are generated and delivered, sometimes it could potentially cause the dapli_thread to hang (trying to lock a word that is not valid). This could severely affect the future processing of connections etc.
Problem conclusion
In the uDAPL code for OFED, there is no provision for the callback (from the lower layers in OFED) to pass back the IA pointer aong with the HCA that caused the asynchronous event. The attached IA pointer with the HCA structure may not be valid. Short of a significant re-design in this area, a simple but effective solution would be to chech the validity of the IA pointer (if it really is an IA). In all other cases we return immediately. This is ok, since our main consumer never processes the asynchronous events anyway.
Temporary fix
Comments
APAR Information
APAR number
IV56852
Reported component name
UDAPL
Reported component ID
5765H4040
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2014-03-19
Closed date
2014-03-19
Last modified date
2014-05-23
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
UDAPL
Fixed component ID
5765H4040
Applicable component levels
R710 PSY U859835
UP14/05/22 I 1000
PTF to Fileset Mapping
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11R","label":"AIX 7.1 HIPERS, APARs and Fixes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
23 May 2014