From: wcheng@sourceware.org <wcheng@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs glock.c
Date: 25 Jan 2007 22:38:39 -0000 [thread overview]
Message-ID: <20070125223839.20409.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: wcheng at sourceware.org 2007-01-25 22:38:39
Modified files:
gfs-kernel/src/gfs: glock.c
Log message:
Bugzilla 214239 - trimming glock
Forgot to increase gl_count in previous check-in.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/glock.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.20.2.4&r2=1.20.2.5
--- cluster/gfs-kernel/src/gfs/glock.c 2007/01/22 07:43:52 1.20.2.4
+++ cluster/gfs-kernel/src/gfs/glock.c 2007/01/25 22:38:39 1.20.2.5
@@ -2550,17 +2550,19 @@
/*
* If the associated inode glock has been in unlocked
- * state for a while, try to purge it.
+ * state, try to purge it.
*/
if (trylock_on_glock(i_gl)) {
if (i_gl->gl_state == LM_ST_UNLOCKED) {
*p_count = *p_count - 1;
unlock_on_glock(i_gl);
+ atomic_inc(&gl->gl_count);
gfs_iopen_go_callback(gl, LM_ST_UNLOCKED);
handle_callback(gl, LM_ST_UNLOCKED);
spin_lock(&gl->gl_spin);
run_queue(gl);
spin_unlock(&gl->gl_spin);
+ glock_put(gl);
} else
unlock_on_glock(i_gl);
}
next reply other threads:[~2007-01-25 22:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 22:38 wcheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-26 17:38 [Cluster-devel] cluster/gfs-kernel/src/gfs glock.c wcheng
2007-06-26 17:50 wcheng
2007-06-26 18:30 wcheng
2007-06-26 18:38 wcheng
2007-06-26 19:42 wcheng
2007-06-26 19:43 wcheng
2007-06-26 20:34 wcheng
2007-06-26 20:39 wcheng
2008-01-24 20:08 bmarzins
2008-01-24 20:25 bmarzins
2008-01-24 20:42 bmarzins
2008-01-24 22:23 bmarzins
2008-01-28 6:40 fabbione
2008-01-29 22:21 bmarzins
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=20070125223839.20409.qmail@sourceware.org \
--to=wcheng@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).