Re: [PATCH] SOCK_SEQPACKET socketpair must get SIGPIPE in AF_UNIX if one end is closed

2016-03-15 Thread Alexander Potapenko
Done, thanks for your response! On Mon, Mar 14, 2016 at 8:19 PM, David Miller wrote: > From: Alexander Potapenko > Date: Wed, 9 Mar 2016 15:10:23 +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

Re: [PATCH] SOCK_SEQPACKET socketpair must get SIGPIPE in AF_UNIX if one end is closed

2016-03-14 Thread David Miller
From: Alexander Potapenko Date: Wed, 9 Mar 2016 15:10:23 +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. > > Signed-off-by: Alexander Potapenko Please format y

[PATCH] SOCK_SEQPACKET socketpair must get SIGPIPE in AF_UNIX if one end is closed

2016-03-09 Thread Alexander Potapenko
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. Signed-off-by: Alexander Potapenko --- I used the following program to check the kernel behavior: /*/ #include