From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH GFS2] Move inode deletion out of blocking_cb
Date: Fri, 14 Sep 2007 13:29:40 +0100 [thread overview]
Message-ID: <1189772980.1068.44.camel@quoit> (raw)
In-Reply-To: <46E9B12A.3070103@redhat.com>
Hi,
On Thu, 2007-09-13 at 17:52 -0400, Wendy Cheng wrote:
> Move inode deletion code out of blocking_cb handle_callback route to
> avoid racy conditions that end up blocking lock_dlm1 thread. Fix
> bugzilla 286821.
>
> -- Wendy
Now in the -nmw git tree. Thanks,
Steve.
prev parent reply other threads:[~2007-09-14 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 21:52 [Cluster-devel] [PATCH GFS2] Move inode deletion out of blocking_cb Wendy Cheng
2007-09-14 12:29 ` Steven Whitehouse [this message]
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=1189772980.1068.44.camel@quoit \
--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).