From: Yihao Wu <wuyihao@linux.alibaba.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>
Cc: caspar@linux.alibaba.com
Subject: Re: [PATCH v2 1/2] NFSv4.1: Again fix a race where CB_NOTIFY_LOCK fails to wake a waiter
Date: Fri, 17 May 2019 22:04:30 +0800 [thread overview]
Message-ID: <129d03a2-2bea-2965-d614-e5622e2e828b@linux.alibaba.com> (raw)
In-Reply-To: <07216eb5-7a15-d7b1-e553-58baa0e07282@linux.alibaba.com>
On 2019/5/17 5:22 PM, Joseph Qi wrote:
> Hi Yihao,
>
> On 19/5/13 14:57, Yihao Wu wrote:
>> Commit b7dbcc0e433f "NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter"
>> found this bug. However it didn't fix it.
>>
>> This commit replaces schedule_timeout() with wait_woken() and
>> default_wake_function() with woken_wake_function() in function
>> nfs4_retry_setlk() and nfs4_wake_lock_waiter(). wait_woken() uses
>> memory barriers in its implementation to avoid potential race condition
>> when putting a process into sleeping state and then waking it up.
>>
>> Fixes: a1d617d8f134 ("nfs: allow blocking locks to be awoken by lock callbacks")
>> Cc: stable@vger.kernel.org #4.9+
>> Signed-off-by: Yihao Wu <wuyihao@linux.alibaba.com>
>> ---
>> fs/nfs/nfs4proc.c | 23 +++++++----------------
>> 1 file changed, 7 insertions(+), 16 deletions(-)
>>
>> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
>> index c29cbef..f9ed6b5 100644
>> --- a/fs/nfs/nfs4proc.c
>> +++ b/fs/nfs/nfs4proc.c
>> @@ -6932,7 +6932,6 @@ struct nfs4_lock_waiter {
>> struct task_struct *task;
>> struct inode *inode;
>> struct nfs_lowner *owner;
>> - bool notified;
>> };
>>
>> static int
>> @@ -6954,13 +6953,13 @@ struct nfs4_lock_waiter {
>> /* Make sure it's for the right inode */
>> if (nfs_compare_fh(NFS_FH(waiter->inode), &cbnl->cbnl_fh))
>> return 0;
>> -
>> - waiter->notified = true;
>> }
>>
>> /* override "private" so we can use default_wake_function */
>> wait->private = waiter->task;
>> - ret = autoremove_wake_function(wait, mode, flags, key);
>> + ret = woken_wake_function(wait, mode, flags, key);
>> + if (ret)
>> + list_del_init(&wait->entry);
>> wait->private = waiter;
>> return ret;
>> }
>> @@ -6979,8 +6978,7 @@ struct nfs4_lock_waiter {
>> .s_dev = server->s_dev };
>> struct nfs4_lock_waiter waiter = { .task = current,
>> .inode = state->inode,
>> - .owner = &owner,
>> - .notified = false };
>> + .owner = &owner};
>> wait_queue_entry_t wait;
>>
>> /* Don't bother with waitqueue if we don't expect a callback */
>> @@ -6993,21 +6991,14 @@ struct nfs4_lock_waiter {
>> add_wait_queue(q, &wait);
>>
>> while(!signalled()) {
>> - waiter.notified = false;
>> status = nfs4_proc_setlk(state, cmd, request);
>> if ((status != -EAGAIN) || IS_SETLK(cmd))
>> break;
>>
>> status = -ERESTARTSYS;
>> - spin_lock_irqsave(&q->lock, flags);
>> - if (waiter.notified) {
>> - spin_unlock_irqrestore(&q->lock, flags);
>> - continue;
>> - }
>> - set_current_state(TASK_INTERRUPTIBLE);
>> - spin_unlock_irqrestore(&q->lock, flags);
>> -
>> - freezable_schedule_timeout(NFS4_LOCK_MAXTIMEOUT);
>> + freezer_do_not_count();
>> + wait_woken(&wait, TASK_INTERRUPTIBLE, NFS4_LOCK_MAXTIMEOUT);
>> + freezer_count();
>
> Since now variable 'flags' is not used anymore, we have to delete it as well.
> Otherwise there is a compile warning “unused variable ‘flags’”.
>
> Thanks,
> Joseph
Thank you Joseph. I'll remove unused 'flags' in PATCH v3.
Thanks,
Yihao Wu
>
>> }
>>
>> finish_wait(q, &wait);
>>
next prev parent reply other threads:[~2019-05-17 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 6:49 [PATCH v2 0/2] Fix two bugs CB_NOTIFY_LOCK failing to wake a water Yihao Wu
2019-05-13 6:57 ` [PATCH v2 1/2] NFSv4.1: Again fix a race where CB_NOTIFY_LOCK fails to wake a waiter Yihao Wu
2019-05-17 9:22 ` Joseph Qi
2019-05-17 14:04 ` Yihao Wu [this message]
2019-05-21 17:57 ` [PATCH v3 " Yihao Wu
2019-05-13 6:58 ` [PATCH v2 2/2] NFSv4.1: Fix bug only first CB_NOTIFY_LOCK is handled Yihao Wu
2019-05-13 13:36 ` [PATCH v2 0/2] Fix two bugs CB_NOTIFY_LOCK failing to wake a water Jeff Layton
2019-05-16 8:01 ` Yihao Wu
2019-05-16 11:47 ` Jeff Layton
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=129d03a2-2bea-2965-d614-e5622e2e828b@linux.alibaba.com \
--to=wuyihao@linux.alibaba.com \
--cc=bfields@fieldses.org \
--cc=caspar@linux.alibaba.com \
--cc=jlayton@kernel.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-nfs@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).