All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org, trond.myklebust@fys.uio.no
Subject: Re: 2.6.18rc5: NFSd possible recursive locking
Date: Mon, 4 Sep 2006 10:03:33 -0400	[thread overview]
Message-ID: <20060904140333.GF6778@redhat.com> (raw)
In-Reply-To: <m3slj8ae84.fsf@defiant.localdomain>

On Sun, Sep 03, 2006 at 10:26:35PM +0200, Krzysztof Halasa wrote:
 > Hi,
 > 
 > another one (details available on request):
 > 
 > [ INFO: possible recursive locking detected ]
 > ---------------------------------------------
 > nfsd/1566 is trying to acquire lock:
 >  (&inode->i_mutex){--..}, at: [<c0334e0c>] mutex_lock+0x1c/0x20
 > 
 > but task is already holding lock:
 >  (&inode->i_mutex){--..}, at: [<c0334e0c>] mutex_lock+0x1c/0x20

This one has been there for a month or so..
http://bugme.osdl.org/show_bug.cgi?id=6918

	Dave
 

  reply	other threads:[~2006-09-04 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 20:26 2.6.18rc5: NFSd possible recursive locking Krzysztof Halasa
2006-09-04 14:03 ` Dave Jones [this message]
2006-09-05  6:12 ` Peter Zijlstra
2006-09-05 18:18   ` Krzysztof Halasa

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=20060904140333.GF6778@redhat.com \
    --to=davej@redhat.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.