public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: teigland@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/group/daemon app.c cpg.c gd_internal.h
Date: Fri, 05 Jan 2007 19:56:00 -0000	[thread overview]
Message-ID: <20070105195609.2026.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL50
Changes by:	teigland@sourceware.org	2007-01-05 19:56:09

Modified files:
	group/daemon   : app.c cpg.c gd_internal.h 

Log message:
	groupd creates uint32 global id's for each group.  It doesn't
	use them itself, but provides them to each registered app to use
	if it wants.  (The dlm and gfs each use the global id in messages
	to distinguish between different lockspaces/fs's.)  groupd's
	method of creating these gid's (local counter | local nodeid)
	can result in duplicate gid's in the cluster given a somewhat
	uncommon sequence of events.
	bz 221629

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/app.c.diff?cvsroot=cluster&only_with_tag=RHEL50&r1=1.52.4.1&r2=1.52.4.2
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/cpg.c.diff?cvsroot=cluster&only_with_tag=RHEL50&r1=1.36.4.1&r2=1.36.4.2
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/gd_internal.h.diff?cvsroot=cluster&only_with_tag=RHEL50&r1=1.44.4.1&r2=1.44.4.2


             reply	other threads:[~2007-01-05 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 19:56 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-05 18:50 teigland
2007-01-05 18:49 teigland
2006-06-22 18:39 teigland
2006-06-21 18:10 teigland
2006-03-03 21:52 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=20070105195609.2026.qmail@sourceware.org \
    --to=teigland@sourceware.org \
    --cc=cluster-cvs@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).