cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] cman: Prevent libcman from causing SIGPIPE
Date: Mon, 17 Dec 2012 09:23:21 +0000	[thread overview]
Message-ID: <50CEE489.8010603@redhat.com> (raw)

If corosync goes down/is shut down cman will return 0 from cman_dispatch 
and close the socket. However, if a cman write operation is issued 
before this happens then SIGPIPE can result from the writev() call to an 
open, but disconnected, FD.

This patch changes writev() to sendmg() so it can pass MSG_NOSIGNAL to 
the system call and prevent SIGPIPEs from occurring.

Signed-Off-By: Christine Caulfield <ccaulfie@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cman_sigpipe.patch
Type: text/x-patch
Size: 579 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20121217/93b59fd5/attachment.bin>

             reply	other threads:[~2012-12-17  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  9:23 Christine Caulfield [this message]
2012-12-17 10:12 ` [Cluster-devel] [PATCH] cman: Prevent libcman from causing SIGPIPE Fabio M. Di Nitto

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=50CEE489.8010603@redhat.com \
    --to=ccaulfie@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).