All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix change nlink deadlock
Date: Fri, 15 Dec 2006 09:50:44 -0500	[thread overview]
Message-ID: <4582B644.4020103@redhat.com> (raw)

Bugzilla 215088

Fix deadlock in gfs2_change_nlink() while installing RHEL5 into GFS2 
partition. The gfs2_rename() apparently needs block allocation for the 
new name (into the directory) where it requires rg locks. At the same 
time, while updating the nlink count for the replaced file, 
gfs2_change_nlink() tries to return the inode meta-data back to resource 
group where it needs rg locks too. Our logic doesn't allow process to 
acquire these locks recursively by the same process  (RHEL installer) 
that results a BUG call. This only happens within rename code path and 
only if the destination file exists before the rename operation.

Patch passed a simulated test program created for this issue yesterday - 
havn't really tried it out on installer yet. Will continue to installer 
test today. Pass it up for a quick eyeball examine.

-- Wendy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2_rename_nlink.patch
Type: text/x-patch
Size: 2580 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20061215/58088dfc/attachment.bin>

             reply	other threads:[~2006-12-15 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-15 14:50 Wendy Cheng [this message]
2006-12-15 15:16 ` [Cluster-devel] [PATCH] Fix change nlink deadlock Steven Whitehouse
2006-12-15 19:44   ` Wendy Cheng
2006-12-18 15:50     ` 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=4582B644.4020103@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.