From: "Rémi Denis-Courmont" <remi@remlab.net>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-media@vger.kernel.org
Subject: Re: gnutv should not ignore SIGPIPE
Date: Fri, 25 Nov 2011 15:34:04 +0200 [thread overview]
Message-ID: <201111251534.05480.remi@remlab.net> (raw)
In-Reply-To: <jao3r9$i9e$1@dough.gmane.org>
Le vendredi 25 novembre 2011 15:05:44 Brian J. Murrell, vous avez écrit :
> Is there a good reason I am not seeing why gnutv should be ignoring
> SIGPIPE?
In general, ignoring SIGPIPE is the easiest way to protect against denial of
service when a peer connection socket is hung up remotely. MSG_NOSIGNAL is a
more modern alternative.
Anyway, the problem is not so mucgh ignoring SIGPIPE as ignoring EPIPE write
errors.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2011-11-25 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 13:05 gnutv should not ignore SIGPIPE Brian J. Murrell
2011-11-25 13:34 ` Rémi Denis-Courmont [this message]
2011-11-25 13:36 ` Brian J. Murrell
2011-11-29 14:22 ` Brian J. Murrell
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=201111251534.05480.remi@remlab.net \
--to=remi@remlab.net \
--cc=brian@interlinx.bc.ca \
--cc=linux-media@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox