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 inode.c inode.h ops ... Date: Wed, 14 Feb 2007 23:15:00 -0000 [thread overview] Message-ID: <20070214231544.12909.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: RHEL4 Changes by: wcheng@sourceware.org 2007-02-14 23:15:44 Modified files: gfs-kernel/src/gfs: inode.c inode.h ops_inode.c Log message: Final patch for bugzilla 1904745 - there is a deadlock documented in the bugzilla entry comment #26 that is messy to get around under current GFS lock order rule. To compromise the issue, we will fail the rename with the original error return code (-ENOENT), if the new ino has any possibility to cause deadlock. This implies, if GFS ino number is allocated via true random manner, we only reduce this error return code by 25%. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/inode.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.20.2.3&r2=1.20.2.4 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/inode.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.3.2.1&r2=1.3.2.2 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.5&r2=1.6.2.6
reply other threads:[~2007-02-14 23:15 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070214231544.12909.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).