Thread (6 messages) flat view 6 messages, 4 authors, 2016-03-18

Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get SIGPIPE

From: David Miller <davem@davemloft.net>
Date: 2016-03-18 22:32:34
Also in: lkml

From: Alexander Potapenko <glider@google.com>
Date: Tue, 15 Mar 2016 10:03:44 +0100
According to IEEE Std 1003.1, 2013, sending data to a SOCK_SEQPACKET
socketpair with MSG_NOSIGNAL flag set must result in a SIGPIPE if the
socket is no longer connected.

I used the following program to check the kernel behavior:
 ...
Signed-off-by: Alexander Potapenko <glider@google.com>
In the final analysis I don't think we can do this.

Properly working programs will start to mysteriously receive
signals in this situation and fail.

I'm sorry but I think we're stuck with this behavior.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help