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] Fix misuse of cman FD in fenced
Date: Thu, 13 Sep 2012 13:26:53 +0100	[thread overview]
Message-ID: <5051D10D.4050702@redhat.com> (raw)

This patch fixes a caching of the cman file descriptor in fenced, which 
the header file explicitly says you should not do.

I have seen symptoms that are consistent with this going wrong and while 
I can't prove that this is the cause it looks highly likely.

The patch is against the RHEL5 branch, but the bug also exists in RHEL6 
and upstream versions

There also is a chance that this mistake exists in other cluster 
daemons, I haven't checked as yet.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_fd.patch
Type: text/x-patch
Size: 1577 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20120913/63fc35f4/attachment.bin>

                 reply	other threads:[~2012-09-13 12:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5051D10D.4050702@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).