From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/daemon daemon.c
Date: 28 Jun 2007 08:07:35 -0000 [thread overview]
Message-ID: <20070628080735.30069.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL50
Changes by: pcaulfield at sourceware.org 2007-06-28 08:07:35
Modified files:
cman/daemon : daemon.c
Log message:
Make sure to cleanup the buffer when processing each request or dirty data
can be passed from one request to another.
Add a barrier to make sure that the socket data are not bigger than the buffer
or we overflow somewhere at random.
21:41 #sistina: < feist> pjc: can you commit that first cman security fix to
RHEL50, (the rpm has already been built, but it would
be nice for tracking purposes).
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/daemon/daemon.c.diff?cvsroot=cluster&only_with_tag=RHEL50&r1=1.32&r2=1.32.4.1
--- cluster/cman/daemon/daemon.c 2006/09/14 13:01:06 1.32
+++ cluster/cman/daemon/daemon.c 2007/06/28 08:07:34 1.32.4.1
@@ -147,6 +147,8 @@
int len;
int totallen = 0;
+ memset(buf, 0, (MAX_CLUSTER_MESSAGE + sizeof(struct sock_header)));
+
len = read(fd, buf, sizeof(struct sock_header));
P_DAEMON("read %d bytes from fd %d\n", len, fd);
@@ -175,6 +177,11 @@
send_status_return(con, msg->command, -EINVAL);
return 0;
}
+ if ((msg->length-len) > MAX_CLUSTER_MESSAGE) {
+ P_DAEMON("message on socket is too big\n");
+ send_status_return(con, msg->command, -EINVAL);
+ return 0;
+ }
totallen = len;
next reply other threads:[~2007-06-28 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 8:07 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 7:39 [Cluster-devel] cluster/cman/daemon daemon.c pcaulfield
2007-06-19 12:32 fabbione
2007-01-08 10:08 pcaulfield
2007-01-08 10:07 pcaulfield
2006-09-14 13:01 pcaulfield
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=20070628080735.30069.qmail@sourceware.org \
--to=pcaulfield@sourceware.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 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.