From: Balaji Rao <balajirrao@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>
Subject: Problem during implementing NFS support
Date: Mon, 21 Jul 2008 00:41:10 +0530 [thread overview]
Message-ID: <200807210041.10609.balajirrao@gmail.com> (raw)
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.
Why can't we allow multiple readers to read a page ?
Please clarify.
Balaji Rao
next reply other threads:[~2008-07-20 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 19:11 Balaji Rao [this message]
2008-07-20 16:43 ` Problem during implementing NFS support David Woodhouse
2008-07-20 19:36 ` Balaji Rao
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=200807210041.10609.balajirrao@gmail.com \
--to=balajirrao@gmail.com \
--cc=chris.mason@oracle.com \
--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