From: Trond Myklebust <trond.myklebust@primarydata.com>
To: stable@vger.kernel.org
Cc: Weston Andros Adamson <dros@primarydata.com>, linux-nfs@vger.kernel.org
Subject: [PATCH 09/14] nfs: fix nonblocking calls to nfs_page_group_lock
Date: Mon, 15 Sep 2014 14:14:40 -0400 [thread overview]
Message-ID: <1410804885-17228-10-git-send-email-trond.myklebust@primarydata.com> (raw)
In-Reply-To: <1410804885-17228-9-git-send-email-trond.myklebust@primarydata.com>
From: Weston Andros Adamson <dros@primarydata.com>
commit bc8a309e88a86205fc3e17f06e42a2e56fc6f807 upstream.
nfs_page_group_lock was calling wait_on_bit_lock even when told not to
block. Fix by first trying test_and_set_bit, followed by wait_on_bit_lock
if and only if blocking is allowed. Return -EAGAIN if nonblocking and the
test_and_set of the bit was already locked.
Signed-off-by: Weston Andros Adamson <dros@primarydata.com>
Reviewed-by: Peng Tao <tao.peng@primarydata.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
---
fs/nfs/pagelist.c | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/fs/nfs/pagelist.c b/fs/nfs/pagelist.c
index b4ebd4d7d976..c27a05c27c11 100644
--- a/fs/nfs/pagelist.c
+++ b/fs/nfs/pagelist.c
@@ -149,24 +149,29 @@ static int nfs_wait_bit_uninterruptible(void *word)
*
* this lock must be held if modifying the page group list
*
- * returns result from wait_on_bit_lock: 0 on success, < 0 on error
+ * return 0 on success, < 0 on error: -EDELAY if nonblocking or the
+ * result from wait_on_bit_lock
+ *
+ * NOTE: calling with nonblock=false should always have set the
+ * lock bit (see fs/buffer.c and other uses of wait_on_bit_lock
+ * with TASK_UNINTERRUPTIBLE), so there is no need to check the result.
*/
int
nfs_page_group_lock(struct nfs_page *req, bool nonblock)
{
struct nfs_page *head = req->wb_head;
- int ret;
WARN_ON_ONCE(head != head->wb_head);
- do {
- ret = wait_on_bit_lock(&head->wb_flags, PG_HEADLOCK,
- nfs_wait_bit_uninterruptible,
- TASK_UNINTERRUPTIBLE);
- } while (!nonblock && ret != 0);
+ if (!test_and_set_bit(PG_HEADLOCK, &head->wb_flags))
+ return 0;
- WARN_ON_ONCE(ret > 0);
- return ret;
+ if (!nonblock)
+ return wait_on_bit_lock(&head->wb_flags, PG_HEADLOCK,
+ nfs_wait_bit_uninterruptible,
+ TASK_UNINTERRUPTIBLE);
+
+ return -EAGAIN;
}
/*
--
1.9.3
next prev parent reply other threads:[~2014-09-15 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 18:14 [PATCH 00/14] Stable fixes for NFS client read/write code in 3.16.x Trond Myklebust
2014-09-15 18:14 ` [PATCH 01/14] nfs: move nfs_pgio_data and remove nfs_rw_header Trond Myklebust
2014-09-15 18:14 ` [PATCH 02/14] nfs: rename members of nfs_pgio_data Trond Myklebust
2014-09-15 18:14 ` [PATCH 03/14] nfs: merge nfs_pgio_data into _header Trond Myklebust
2014-09-15 18:14 ` [PATCH 04/14] nfs: remove pgio_header refcount, related cleanup Trond Myklebust
2014-09-15 18:14 ` [PATCH 05/14] nfs: check wait_on_bit_lock err in page_group_lock Trond Myklebust
2014-09-15 18:14 ` [PATCH 06/14] pnfs: add pnfs_put_lseg_async Trond Myklebust
2014-09-15 18:14 ` [PATCH 07/14] nfs: clear_request_commit while holding i_lock Trond Myklebust
2014-09-15 18:14 ` [PATCH 08/14] nfs: change nfs_page_group_lock argument Trond Myklebust
2014-09-15 18:14 ` Trond Myklebust [this message]
2014-09-15 18:14 ` [PATCH 10/14] nfs: use blocking page_group_lock in add_request Trond Myklebust
2014-09-15 18:14 ` [PATCH 11/14] nfs: fix error handling in lock_and_join_requests Trond Myklebust
2014-09-15 18:14 ` [PATCH 12/14] nfs: don't sleep with inode lock " Trond Myklebust
2014-09-15 18:14 ` [PATCH 13/14] nfs: disallow duplicate pages in pgio page vectors Trond Myklebust
2014-09-15 18:14 ` [PATCH 14/14] nfs: can_coalesce_requests must enforce contiguity Trond Myklebust
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=1410804885-17228-10-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=dros@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).