From: Vasily Averin <vvs@virtuozzo.com>
To: Jeff Layton <jlayton@kernel.org>, linux-nfs@vger.kernel.org
Cc: chuck.lever@oracle.com, bfields@fieldses.org
Subject: Re: [PATCH] nfsd: don't put blocked locks on LRU until after vfs_lock_file returns
Date: Tue, 23 Nov 2021 18:20:08 +0300 [thread overview]
Message-ID: <d3f68639-3f07-dbf7-9a4d-984fdd7bd62f@virtuozzo.com> (raw)
In-Reply-To: <20211123122223.69236-1-jlayton@kernel.org>
On 23.11.2021 15:22, Jeff Layton wrote:
> Vasily reported a case where vfs_lock_file took a very long time to
> return (longer than a lease period). The laundromat eventually ran and
> reaped the thing and when the vfs_lock_file returned, it ended up
> accessing freed memory.
>
> Don't put entries onto the LRU until vfs_lock_file returns.
Cc: stable@vger.kernel.org
Fixes: 7919d0a27f1e "nfsd: add a LRU list for blocked locks"
> Reported-by: Vasily Averin <vvs@virtuozzo.com>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Tested-by: Vasily Averin <vvs@virtuozzo.com>
> ---
> fs/nfsd/nfs4state.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index bfad94c70b84..8cfef84b9355 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -6966,10 +6966,8 @@ nfsd4_lock(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
> }
>
> if (fl_flags & FL_SLEEP) {
> - nbl->nbl_time = ktime_get_boottime_seconds();
> spin_lock(&nn->blocked_locks_lock);
> list_add_tail(&nbl->nbl_list, &lock_sop->lo_blocked);
> - list_add_tail(&nbl->nbl_lru, &nn->blocked_locks_lru);
> spin_unlock(&nn->blocked_locks_lock);
> }
>
> @@ -6982,6 +6980,10 @@ nfsd4_lock(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
> nn->somebody_reclaimed = true;
> break;
> case FILE_LOCK_DEFERRED:
> + nbl->nbl_time = ktime_get_boottime_seconds();
> + spin_lock(&nn->blocked_locks_lock);
> + list_add_tail(&nbl->nbl_lru, &nn->blocked_locks_lru);
> + spin_unlock(&nn->blocked_locks_lock);
> nbl = NULL;
> fallthrough;
> case -EAGAIN: /* conflock holds conflicting lock */
>
next prev parent reply other threads:[~2021-11-23 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 12:22 [PATCH] nfsd: don't put blocked locks on LRU until after vfs_lock_file returns Jeff Layton
2021-11-23 15:20 ` Vasily Averin [this message]
2021-11-23 15:21 ` Chuck Lever III
2021-11-23 15:59 ` J. Bruce Fields
2021-11-23 16:31 ` Jeff Layton
2021-11-23 16:41 ` J. Bruce Fields
2021-11-23 17:02 ` 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=d3f68639-3f07-dbf7-9a4d-984fdd7bd62f@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--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