From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH][GFS2] GFS2 - patch to check for recursive lock requests in gfs2_rename code path
Date: Fri, 30 Nov 2007 08:42:33 +0000 [thread overview]
Message-ID: <1196412153.1068.914.camel@quoit> (raw)
In-Reply-To: <474F1D82.4040404@redhat.com>
Hi,
On Thu, 2007-11-29 at 14:13 -0600, Abhijith Das wrote:
> A certain scenario in the rename code path triggers a kernel BUG()
> because it accidentally does recursive locking The first lock is
> requested to unlink an already existing inode (replacing a file) and the
> second lock is requested when the destination directory needs to alloc
> some space. It is rare that these two
> events happen during the same rename call, and even more rare that these
> two instances try to lock the same rgrp. It is, however, possible.
> https://bugzilla.redhat.com/show_bug.cgi?id=404711
>
> Signed-off-by: Abhijith Das <adas@redhat.com>
Applied to the -nmw git tree. Thanks,
Steve.
prev parent reply other threads:[~2007-11-30 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 20:13 [Cluster-devel] [PATCH][GFS2] GFS2 - patch to check for recursive lock requests in gfs2_rename code path Abhijith Das
2007-11-30 8:42 ` 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=1196412153.1068.914.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 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.