From: Trond Myklebust <trondmy@hammerspace.com>
To: "dai.ngo@oracle.com" <dai.ngo@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] NFSv4: can_open_cached needs to be called with so_lock
Date: Fri, 30 Apr 2021 12:42:52 +0000 [thread overview]
Message-ID: <8fadf7c12b188eacf5c2bb577a2fbf938e51ebaa.camel@hammerspace.com> (raw)
In-Reply-To: <20210430050900.106851-1-dai.ngo@oracle.com>
On Fri, 2021-04-30 at 01:09 -0400, Dai Ngo wrote:
> Currently can_open_cached accesses the openstate's flags without the
> so_lock and also does not update the flags of the cached state. This
> results in the openstate's flags be out of sync which can cause the
> file to be closed prematurely.
>
> This patch adds the missing so_lock around the call to
> can_open_cached
> and also updates the openstate's flags if the cached openstate is
> used.
>
> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> ---
> fs/nfs/nfs4proc.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index c65c4b41e2c1..2464e77c51f9 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -2410,9 +2410,15 @@ static void nfs4_open_prepare(struct rpc_task
> *task, void *calldata)
> if (data->state != NULL) {
> struct nfs_delegation *delegation;
>
> + spin_lock(&data->state->owner->so_lock);
> if (can_open_cached(data->state, data->o_arg.fmode,
> - data->o_arg.open_flags,
> claim))
> + data->o_arg.open_flags, claim)) {
> + update_open_stateflags(data->state, data-
> >o_arg.fmode);
> + spin_unlock(&data->state->owner->so_lock);
> goto out_no_action;
> + }
> + spin_unlock(&data->state->owner->so_lock);
> +
> rcu_read_lock();
> delegation = nfs4_get_valid_delegation(data->state-
> >inode);
> if (can_open_delegated(delegation, data->o_arg.fmode,
> claim))
This is going to introduce stateid leaks. The actual update of the open
state flags happens in nfs4_try_open_cached(), which is called from
nfs4_opendata_to_nfs4_state().
While we could put spinlocks around the call to can_open_cached() here,
there is little point in doing so, since this is just a read-only
advisory check. The real check is performed, as I said, in
nfs4_try_open_cached().
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2021-04-30 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 5:09 [PATCH 1/1] NFSv4: can_open_cached needs to be called with so_lock Dai Ngo
2021-04-30 12:42 ` Trond Myklebust [this message]
2021-04-30 16:19 ` dai.ngo
2021-04-30 17:24 ` dai.ngo
2021-04-30 17:56 ` Trond Myklebust
2021-04-30 19:10 ` dai.ngo
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=8fadf7c12b188eacf5c2bb577a2fbf938e51ebaa.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=dai.ngo@oracle.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