tNetTask deadly embrace via the log client
Bug #541116 reported by
Jeff Hill
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| EPICS Base |
Fix Released
|
High
|
Jeff Hill | ||
Bug Description
In low network buffer situations the tNetTask vxWorks IP kernel system thread prints messages using the logMsg()call. The EPICS log client uses logFdAdd to cause the logMsg() messages to be sent also to the ioc log server. However, if the tNetTask blocks attempting to deliver a message to the network in a low mbuf situation then the IP kernel may become deadlocked.
Additional information:
This bug probably exists in all previous versions of EPICS
Original Mantis Bug: mantis-35
http://
Revision history for this message
| Jeff Hill (johill-lanl) wrote | #1 |
Revision history for this message
| Andrew Johnson (anj) wrote | #2 |
To post a comment you must log in.
The solution chosen was to create a vxWorks device driver that
calls errlogPrintf for each write request. LogfdAdd is called
for an instance of this device. The LogFdAdd call in the log
client was remioved.
Fixed in R3.13.9