public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: wcheng@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs-kernel/src/gfs ops_inode.c Date: Thu, 18 Jan 2007 20:40:00 -0000 [thread overview] Message-ID: <20070118204012.12633.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: RHEL4 Changes by: wcheng@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
next reply other threads:[~2007-01-18 20:40 UTC|newest] Thread overview: 17+ 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 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 2006-03-08 20:47 bmarzins 2005-09-27 22:51 cfeist 2005-09-27 18:45 bmarzins 2005-09-27 18:44 bmarzins 2005-09-27 18:36 bmarzins 2005-09-09 19:22 bmarzins 2005-09-09 16:54 bmarzins 2005-08-31 4:33 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=20070118204012.12633.qmail@sourceware.org \ --to=wcheng@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: linkBe 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).