From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH GFS2] Move inode deletion out of blocking_cb
Date: Thu, 13 Sep 2007 17:52:42 -0400 [thread overview]
Message-ID: <46E9B12A.3070103@redhat.com> (raw)
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2_callback.patch
Type: text/x-patch
Size: 772 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070913/0d186da6/attachment.bin>
next reply other threads:[~2007-09-13 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 21:52 Wendy Cheng [this message]
2007-09-14 12:29 ` [Cluster-devel] [PATCH GFS2] Move inode deletion out of blocking_cb Steven Whitehouse
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=46E9B12A.3070103@redhat.com \
--to=wcheng@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).