From: Matthew Wilcox <matthew@wil.cx>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: viro@zeniv.linux.org.uk, dchinner@redhat.com,
Trond.Myklebust@netapp.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] Add unlocked version of igrab.
Date: Sun, 27 Mar 2011 20:54:23 -0600 [thread overview]
Message-ID: <20110328025423.GN13806@parisc-linux.org> (raw)
In-Reply-To: <1301277361-9453-2-git-send-email-ryan@bluewatersys.com>
On Mon, Mar 28, 2011 at 02:56:00PM +1300, Ryan Mallon wrote:
> Commit 250df6ed274d767da844a5d9f05720b804240197 "fs: protect
> inode->i_state with inode->i_lock" changes igrab to acquire inode->i_lock,
> however some callees, notably nfs_inode_add_request, already hold the lock
> when calling igrab.
I think a better solution to your problem is to notice that this is
called in the context of doing a write to an inode. That means we
must already have a reference count on this inode, so it can't possibly
be in I_FREEING or I_WILL_FREE. That means we can just call __iget()
instead ... except that __iget isn't exported to modules.
So we could just bump the refcount by hand ... or we could
EXPORT_SYMBOL(__iget).
Or Al's going to swear a lot about what NFS is doing here and how it's
utterly misdesigned. Anyway, this patch could be part of the solution.
diff --git a/fs/nfs/write.c b/fs/nfs/write.c
index 85d7525..330cef3 100644
--- a/fs/nfs/write.c
+++ b/fs/nfs/write.c
@@ -390,7 +390,7 @@ static int nfs_inode_add_request(struct inode *inode, struct nfs_page *req)
error = radix_tree_insert(&nfsi->nfs_page_tree, req->wb_index, req);
BUG_ON(error);
if (!nfsi->npages) {
- igrab(inode);
+ __iget(inode);
if (nfs_have_delegation(inode, FMODE_WRITE))
nfsi->change_attr++;
}
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2011-03-28 2:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 1:55 [RFC PATCH 0/2] Introduce unlocked version of igrab Ryan Mallon
2011-03-28 1:56 ` [RFC PATCH 1/2] Add " Ryan Mallon
2011-03-28 2:54 ` Matthew Wilcox [this message]
2011-03-28 4:39 ` Ryan Mallon
2011-03-28 5:19 ` [PATCH] fs: don't use igrab() while holding i_lock (was Re: [RFC PATCH 1/2] Add unlocked version of igrab.) Dave Chinner
2011-03-28 1:56 ` [RFC PATCH 2/2] Use __igrab instead of igrab in nfs_inode_add_request Ryan Mallon
2011-03-28 4:43 ` [RFC PATCH 0/2] Introduce unlocked version of igrab Dave Chinner
2011-03-28 4:47 ` Ryan Mallon
2011-03-28 5:03 ` Ryan Mallon
2011-03-28 6:01 ` Dave Chinner
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=20110328025423.GN13806@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Trond.Myklebust@netapp.com \
--cc=dchinner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ryan@bluewatersys.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).