From: "J. Bruce Fields" <bfields@fieldses.org>
To: Scott Mayhew <smayhew@redhat.com>
Cc: chuck.lever@oracle.com, jamie@audible.transient.net,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3] nfsd: Fix cld_net->cn_tfm initialization
Date: Tue, 12 Nov 2019 15:00:36 -0500 [thread overview]
Message-ID: <20191112200036.GC8095@fieldses.org> (raw)
In-Reply-To: <20191112190143.12624-1-smayhew@redhat.com>
Thanks, applied.--b.
On Tue, Nov 12, 2019 at 02:01:43PM -0500, Scott Mayhew wrote:
> Don't assign an error pointer to cld_net->cn_tfm, otherwise an oops will
> occur in nfsd4_remove_cld_pipe().
>
> Also, move the initialization of cld_net->cn_tfm so that it occurs after
> the check to see if nfsdcld is running. This is necessary because
> nfsd4_client_tracking_init() looks for -ETIMEDOUT to determine whether
> to use the "old" nfsdcld tracking ops.
>
> Fixes: 6ee95d1c8991 ("nfsd: add support for upcall version 2")
> Reported-by: Jamie Heilman <jamie@audible.transient.net>
> Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> ---
> fs/nfsd/nfs4recover.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/fs/nfsd/nfs4recover.c b/fs/nfsd/nfs4recover.c
> index cdc75ad4438b..c35c0ebaf722 100644
> --- a/fs/nfsd/nfs4recover.c
> +++ b/fs/nfsd/nfs4recover.c
> @@ -1578,6 +1578,7 @@ nfsd4_cld_tracking_init(struct net *net)
> struct nfsd_net *nn = net_generic(net, nfsd_net_id);
> bool running;
> int retries = 10;
> + struct crypto_shash *tfm;
>
> status = nfs4_cld_state_init(net);
> if (status)
> @@ -1586,11 +1587,6 @@ nfsd4_cld_tracking_init(struct net *net)
> status = __nfsd4_init_cld_pipe(net);
> if (status)
> goto err_shutdown;
> - nn->cld_net->cn_tfm = crypto_alloc_shash("sha256", 0, 0);
> - if (IS_ERR(nn->cld_net->cn_tfm)) {
> - status = PTR_ERR(nn->cld_net->cn_tfm);
> - goto err_remove;
> - }
>
> /*
> * rpc pipe upcalls take 30 seconds to time out, so we don't want to
> @@ -1607,6 +1603,12 @@ nfsd4_cld_tracking_init(struct net *net)
> status = -ETIMEDOUT;
> goto err_remove;
> }
> + tfm = crypto_alloc_shash("sha256", 0, 0);
> + if (IS_ERR(tfm)) {
> + status = PTR_ERR(tfm);
> + goto err_remove;
> + }
> + nn->cld_net->cn_tfm = tfm;
>
> status = nfsd4_cld_get_version(nn);
> if (status == -EOPNOTSUPP)
> --
> 2.17.2
prev parent reply other threads:[~2019-11-12 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 19:01 [PATCH v3] nfsd: Fix cld_net->cn_tfm initialization Scott Mayhew
2019-11-12 20:00 ` J. Bruce Fields [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=20191112200036.GC8095@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jamie@audible.transient.net \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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