From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fix for unlink deadlock
Date: Tue, 30 Jan 2007 13:18:47 +0000 [thread overview]
Message-ID: <1170163127.11001.164.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <1170112424.28100.124.camel@xenon.msp.redhat.com>
Hi,
On Mon, 2007-01-29 at 17:13 -0600, Russell Cattelan wrote:
> Note the current glock code in the tree is completely busted
> and will dead lock almost immediately.
>
> I have reverted several changes to glock.c and have
> tested this patch with the older glock code.
> dbench will now run through to completion.
>
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217356
Now applied to the -nmw git tree. I think the way to get around the
problem with not knowing whether the link count will hit zero is just to
remove the code which changes the link count from gfs2_change_nlink and
to turn that into a function which just syncs the current link count to
the on-disk inode.
It would also solve the problem of needing to work out whether to use
inc_nlink() or dec_nlink() to make the change to the link count. Due to
the forthcoming read-only bind mounts work, we must always use the
macros to change the link count rather than doing it directly.
Steve.
next prev parent reply other threads:[~2007-01-30 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 23:13 [Cluster-devel] Fix for unlink deadlock Russell Cattelan
2007-01-30 13:18 ` Steven Whitehouse [this message]
2007-02-01 0:17 ` Wendy Cheng
2007-02-01 0:22 ` Wendy Cheng
2007-02-01 0:46 ` Russell Cattelan
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=1170163127.11001.164.camel@quoit.chygwyn.com \
--to=swhiteho@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 NNTP newsgroup(s).