From: wcheng@sourceware.org <wcheng@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs ops_inode.c
Date: 18 Jan 2007 20:40:12 -0000 [thread overview]
Message-ID: <20070118204012.12641.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: wcheng at sourceware.org 2007-01-18 20:40:12
Modified files:
gfs-kernel/src/gfs: ops_inode.c
Log message:
bugzilla 190475 (rename 3-2):
This patch fixes:
Current rename doesn't lock the (to be deleted) source file during
rename operation unless the source is a directory. This issue would
not show up in a single node case since VFS layer has done its i_sem/
i_mutex locks for both directories and involved files.
This patch excludes a previous proposed change (in the draft patch sent
out for review in cluster-devel list) that adds gfs rename global lock
to prevent a rare case of cluster deadlock. Since cluster rename global
lock is very expensive, we prefer to find other means to fix that issue.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_inode.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.6.2.4&r2=1.6.2.5
--- cluster/gfs-kernel/src/gfs/ops_inode.c 2006/10/10 18:35:27 1.6.2.4
+++ cluster/gfs-kernel/src/gfs/ops_inode.c 2007/01/18 20:40:12 1.6.2.5
@@ -968,15 +968,19 @@
goto fail;
}
- gfs_holder_init(odip->i_gl, LM_ST_EXCLUSIVE, 0, &ghs[0]);
- gfs_holder_init(ndip->i_gl, LM_ST_EXCLUSIVE, 0, &ghs[1]);
- num_gh = 2;
-
- if (nip)
- gfs_holder_init(nip->i_gl, LM_ST_EXCLUSIVE, 0, &ghs[num_gh++]);
+ num_gh = 1;
+ gfs_holder_init(odip->i_gl, LM_ST_EXCLUSIVE, 0, ghs);
+ if (odip != ndip) {
+ gfs_holder_init(ndip->i_gl, LM_ST_EXCLUSIVE, 0, ghs+num_gh);
+ num_gh++;
+ }
+ gfs_holder_init(ip->i_gl, LM_ST_EXCLUSIVE, 0, ghs+num_gh);
+ num_gh++;
- if (dir_rename)
- gfs_holder_init(ip->i_gl, LM_ST_EXCLUSIVE, 0, &ghs[num_gh++]);
+ if (nip) {
+ gfs_holder_init(nip->i_gl, LM_ST_EXCLUSIVE, 0, ghs + num_gh);
+ num_gh++;
+ }
error = gfs_glock_nq_m(num_gh, ghs);
if (error)
next reply other threads:[~2007-01-18 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 20:40 wcheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-11 22:15 [Cluster-devel] cluster/gfs-kernel/src/gfs ops_inode.c rpeterso
2007-07-11 21:58 rpeterso
2007-06-29 21:57 rpeterso
2007-06-05 18:21 wcheng
2007-06-05 17:46 wcheng
2006-10-23 20:47 bmarzins
2006-10-15 7:25 wcheng
2006-10-03 17:27 rohara
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=20070118204012.12641.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).