There are various stages during the OPEN of a PIPE device where system calls in the forked off child process (e.g. dup2() and execl()) might fail. In that case, a DEVOPENFAIL message is sent to the syslog by the child process and it terminates. This message contains the device name supplied to the OPEN command. But this could contain garbage in some cases as at the time the message is generated, the structures containing the device name have already been freed.
Draft Release Note
DEVOPENFAIL messages in the syslog correctly identify the device name and system error number in case of errors during OPEN of a PIPE device. Previously, they could contain a garbage device name and/or system error number/text in some cases.
Final Release Note
Description
There are various stages during the OPEN of a PIPE device where system calls in the forked off child process (e.g. dup2() and execl()) might fail. In that case, a DEVOPENFAIL message is sent to the syslog by the child process and it terminates. This message contains the device name supplied to the OPEN command. But this could contain garbage in some cases as at the time the message is generated, the structures containing the device name have already been freed.
Draft Release Note
DEVOPENFAIL messages in the syslog correctly identify the device name and system error number in case of errors during OPEN of a PIPE device. Previously, they could contain a garbage device name and/or system error number/text in some cases.