From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: Tomasz Kvarsin <kvarsin@gmail.com>,
linux-kernel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: JFS: possible recursive locking detected
Date: Tue, 09 Jan 2007 13:56:14 +0000 [thread overview]
Message-ID: <1168350974.13500.5.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <45A3613F.1050604@in.ibm.com>
On Tue, 2007-01-09 at 15:02 +0530, Srinivasa Ds wrote:
> Tomasz Kvarsin wrote:
> > This I got during boot with 2.6.20-rc4:
> > =============================================
> > [ INFO: possible recursive locking detected ]
...
> So below patch should fix this problem,please test this. Let me know
> your comments on this.
I'm sure there are several other places in the jfs code that need the
same treatment. I've put this off too long already. I'll get a
comprehensive lock annotation patch out today, starting with this one.
>
> Signed-off-by: Srinivasa DS <srinivasa@in.ibm.com>
Thanks,
Shaggy
>
>
> plain text document attachment (jfs.fix)
> namei.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux-2.6.20-rc4/fs/jfs/namei.c
> ===================================================================
> --- linux-2.6.20-rc4.orig/fs/jfs/namei.c
> +++ linux-2.6.20-rc4/fs/jfs/namei.c
> @@ -104,8 +104,8 @@ static int jfs_create(struct inode *dip,
>
> tid = txBegin(dip->i_sb, 0);
>
> - mutex_lock(&JFS_IP(dip)->commit_mutex);
> - mutex_lock(&JFS_IP(ip)->commit_mutex);
> + mutex_lock_nested(&JFS_IP(dip)->commit_mutex, I_MUTEX_PARENT);
> + mutex_lock_nested(&JFS_IP(ip)->commit_mutex, I_MUTEX_CHILD);
>
> rc = jfs_init_acl(tid, ip, dip);
> if (rc)
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2007-01-09 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 7:33 Tomasz Kvarsin
2007-01-09 9:32 ` Srinivasa Ds
2007-01-09 13:56 ` Dave Kleikamp [this message]
2007-01-09 18:05 ` [PATCH] " Dave Kleikamp
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=1168350974.13500.5.camel@kleikamp.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=akpm@osdl.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=kvarsin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasa@in.ibm.com \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®