cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman-kernel/src sm_barrier.c
Date: 25 Sep 2006 15:23:01 -0000	[thread overview]
Message-ID: <20060925152301.32199.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	STABLE
Changes by:	teigland at sourceware.org	2006-09-25 15:23:01

Modified files:
	cman-kernel/src: sm_barrier.c 

Log message:
	process_startdone_barrier_new() can be called when sg->sevent is
	NULL, but we weren't checking for NULL and just deferencing the
	sev->flags which led to oops in bz 206212.
	(sync with RHEL4 branch)

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman-kernel/src/sm_barrier.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.1.6.1.2.1&r2=1.1.6.1.2.2

--- cluster/cman-kernel/src/Attic/sm_barrier.c	2005/06/22 04:41:52	1.1.6.1.2.1
+++ cluster/cman-kernel/src/Attic/sm_barrier.c	2006/09/25 15:23:01	1.1.6.1.2.2
@@ -141,6 +141,12 @@
 {
 	sm_sevent_t *sev = sg->sevent;
 
+	if (!sev) {
+		log_error(sg, "process_startdone_barrier_new: no sev %d",
+			  status);
+		return;
+	}
+
 	if (!test_and_clear_bit(SEFL_ALLOW_BARRIER, &sev->se_flags)) {
 		log_debug(sev->se_sg, "ignore barrier cb status %d", status);
 		return;



             reply	other threads:[~2006-09-25 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 15:23 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-13 14:46 [Cluster-devel] cluster/cman-kernel/src sm_barrier.c teigland

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=20060925152301.32199.qmail@sourceware.org \
    --to=teigland@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 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).