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

From	David Miller <davem@davemloft.net>
Newsgroups	linux.kernel
Subject	Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get SIGPIPE
Date	2016-03-18 23:40 +0100
Message-ID	<rebdN-2ht-25@gated-at.bofh.it> (permalink)
References	<rcT9f-8rY-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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.

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get  SIGPIPE David Miller <davem@davemloft.net> - 2016-03-18 23:40 +0100

csiph-web