public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Balaji Rao <balajirrao@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Problem during implementing NFS support
Date: Mon, 21 Jul 2008 01:06:55 +0530	[thread overview]
Message-ID: <200807210106.56056.balajirrao@gmail.com> (raw)
In-Reply-To: <1216572230.2475.106.camel@shinybook.infradead.org>

On Sunday 20 July 2008 10:13:50 pm David Woodhouse wrote:
> On Mon, 2008-07-21 at 00:41 +0530, Balaji Rao wrote:
> > Hi,
> >
> > There's a problem in btrfs_readdir that tries to lock a root node with
> > one being held. This happens when NFS calls vfs_readdir function with a
> > nfs specific filldir function pointer. This filldir function, called with
> > the lock held calls btrfs_lookup, which tries to take the same lock. So,
> > it keeps waiting on lock_page indefinitely - a deadlock. This is not seen
> > if the inode is RAM in which case, lookup is not called.
>
> We've seen precisely this problem (nfs3 readdirplus calling ->lookup
> from within ->readdir and deadlocking) in a number of other file
> systems.
>
oh, ok!

> I have an evil workaround hack for JFFS2 at
> http://lists.infradead.org/pipermail/linux-mtd/2007-March/017663.html
>
The idea of the patch seems correct to me, that once we "own" the lock, an 
attempt to take it again should be a nop.

Balaji

  reply	other threads:[~2008-07-20 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 19:11 Problem during implementing NFS support Balaji Rao
2008-07-20 16:43 ` David Woodhouse
2008-07-20 19:36   ` Balaji Rao [this message]
2008-07-20 20:08     ` David Woodhouse
2008-07-21  8:10   ` Christoph Hellwig
2008-07-21 12:58     ` Chris Mason

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=200807210106.56056.balajirrao@gmail.com \
    --to=balajirrao@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-btrfs@vger.kernel.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