public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/gfs-kernel/src/gfs glock.c
Date: Thu, 24 Jan 2008 20:42:00 -0000	[thread overview]
Message-ID: <20080124204201.1792.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	bmarzins@sourceware.org	2008-01-24 20:42:01

Modified files:
	gfs-kernel/src/gfs: glock.c 

Log message:
	Fix for bz #426291.  gfs_glock_dq was traversing the gl_holders list without
	holding the gl_spin spinlock, this was causing a problem when the list item
	it was currently looking at got removed from the list.  The solution is to
	not traverse the list, because it is unncessary. Unfortunately, there is also
	a bug in this section of code, where you can't guarantee that you will not
	cache a glock held with GL_NOCACHE.  Fixing this issue requires significantly
	more work.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/glock.c.diff?cvsroot=cluster&r1=1.35&r2=1.36


             reply	other threads:[~2008-01-24 20:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 20:42 bmarzins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 22:21 bmarzins
2008-01-28  6:40 fabbione
2008-01-24 22:23 bmarzins
2008-01-24 20:25 bmarzins
2008-01-24 20:08 bmarzins
2007-06-26 20:39 wcheng
2007-06-26 20:34 wcheng
2007-06-26 19:44 wcheng
2007-06-26 19:42 wcheng
2007-06-26 18:38 wcheng
2007-06-26 18:30 wcheng
2007-06-26 17:50 wcheng
2007-06-26 17:38 wcheng
2007-01-25 22:38 wcheng
2006-05-17 15:28 adas
2006-05-17 15:27 adas
2006-05-17 15:26 adas
2006-05-15 23:07 adas
2006-05-15 23:01 adas
2006-05-15 22:58 adas
2005-10-06 22:32 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=20080124204201.1792.qmail@sourceware.org \
    --to=bmarzins@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).