linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Bruce Fields <bfields@fieldses.org>
Cc: slawek1211@gmail.com, NeilBrown <neilb@suse.com>,
	"open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: wake waiters blocked on file_lock before deleting it
Date: Sat, 20 Apr 2019 06:19:21 -0400	[thread overview]
Message-ID: <CAOhYWNJ6HJP5XB4jrg7_mTs1bCrc_5tzMjgdTu-6+v2+-ABkLw@mail.gmail.com> (raw)
In-Reply-To: <20190420101548.8552-1-jlayton@kernel.org>

On Sat, Apr 20, 2019 at 6:16 AM Jeff Layton <jlayton@kernel.org> wrote:
>
> After a blocked nfsd file_lock request is deleted, knfsd will send a
> callback to the client and then free the request. Commit 16306a61d3b7
> ("fs/locks: always delete_block after waiting.") changed it such that
> locks_delete_block is always called on a request after it is awoken,
> but that patch missed fixing up blocked nfsd request handling.
>
> Call locks_delete_block on the block to wake up any locks still blocked
> on the nfsd lock request before sending the callback.
>
> URL: https://bugzilla.kernel.org/show_bug.cgi?id=203363
> Fixes: 16306a61d3b7 ("fs/locks: always delete_block after waiting.")
> Reported-by: Slawomir Pryczek <slawek1211@gmail.com>
> Cc: Neil Brown <neilb@suse.com>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>  fs/nfsd/nfs4state.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 6a45fb00c5fc..1960e8fd9ad1 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -298,6 +298,14 @@ remove_blocked_locks(struct nfs4_lockowner *lo)
>         }
>  }
>
> +static void
> +nfsd4_cb_notify_lock_prepare(struct nfsd4_callback *cb)
> +{
> +       struct nfsd4_blocked_lock       *nbl = container_of(cb,
> +                                               struct nfsd4_blocked_lock, nbl_cb);
> +       locks_delete_block(&nbl->nbl_lock);
> +}
> +
>  static int
>  nfsd4_cb_notify_lock_done(struct nfsd4_callback *cb, struct rpc_task *task)
>  {
> @@ -325,6 +333,7 @@ nfsd4_cb_notify_lock_release(struct nfsd4_callback *cb)
>  }
>
>  static const struct nfsd4_callback_ops nfsd4_cb_notify_lock_ops = {
> +       .prepare        = nfsd4_cb_notify_lock_prepare,
>         .done           = nfsd4_cb_notify_lock_done,
>         .release        = nfsd4_cb_notify_lock_release,
>  };
> --
> 2.20.1
>

This should also go to stable I think. If you end up picking this up,
can you add the Cc: for stable as well?

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2019-04-20 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 10:15 [PATCH] nfsd: wake waiters blocked on file_lock before deleting it Jeff Layton
2019-04-20 10:19 ` Jeff Layton [this message]

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=CAOhYWNJ6HJP5XB4jrg7_mTs1bCrc_5tzMjgdTu-6+v2+-ABkLw@mail.gmail.com \
    --to=jlayton@kernel.org \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=slawek1211@gmail.com \
    /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).