All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: glider@google.com
Cc: edumazet@google.com, rweikusat@mobileactivedefense.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get SIGPIPE
Date: Fri, 18 Mar 2016 18:32:30 -0400 (EDT)	[thread overview]
Message-ID: <20160318.183230.1601751551897264970.davem@davemloft.net> (raw)
In-Reply-To: <1458032624-139688-1-git-send-email-glider@google.com>

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.

      parent reply	other threads:[~2016-03-18 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  9:03 [PATCH] af_unix: closed SOCK_SEQPACKET socketpair must get SIGPIPE Alexander Potapenko
2016-03-15 13:20 ` Eric Dumazet
2016-03-15 14:35   ` Alexander Potapenko
2016-03-15 13:46 ` David Laight
2016-03-15 13:46   ` David Laight
2016-03-15 16:13   ` Alexander Potapenko
2016-03-15 16:13     ` Alexander Potapenko
2016-03-18 22:32 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160318.183230.1601751551897264970.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rweikusat@mobileactivedefense.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.