From: Trond Myklebust <trondmy@hammerspace.com>
To: "caihuoqing@baidu.com" <caihuoqing@baidu.com>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: [PATCH] NFSD: Make use of the helper macro kthread_run()
Date: Thu, 21 Oct 2021 13:27:32 +0000 [thread overview]
Message-ID: <b481c093912de062aee6ea456dcd6849e7515cbf.camel@hammerspace.com> (raw)
In-Reply-To: <20211021084206.2236-1-caihuoqing@baidu.com>
On Thu, 2021-10-21 at 16:42 +0800, Cai Huoqing wrote:
> [You don't often get email from caihuoqing@baidu.com. Learn why this
> is important at http://aka.ms/LearnAboutSenderIdentification.]
>
> Repalce kthread_create/wake_up_process() with kthread_run()
> to simplify the code.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
> fs/nfsd/nfs4proc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index a36261f89bdf..69428cb31a55 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -1685,15 +1685,15 @@ nfsd4_copy(struct svc_rqst *rqstp, struct
> nfsd4_compound_state *cstate,
> memcpy(©->cp_res.cb_stateid, ©-
> >cp_stateid.stid,
> sizeof(copy->cp_res.cb_stateid));
> dup_copy_fields(copy, async_copy);
> - async_copy->copy_task =
> kthread_create(nfsd4_do_async_copy,
> - async_copy, "%s", "copy thread");
> + async_copy->copy_task =
> kthread_run(nfsd4_do_async_copy,
> + async_copy, "%s",
> + "copy thread");
> if (IS_ERR(async_copy->copy_task))
> goto out_err;
> spin_lock(&async_copy->cp_clp->async_lock);
> list_add(&async_copy->copies,
> &async_copy->cp_clp->async_copies);
> spin_unlock(&async_copy->cp_clp->async_lock);
> - wake_up_process(async_copy->copy_task);
> status = nfs_ok;
> } else {
> status = nfsd4_do_copy(copy, 1);
> --
> 2.25.1
>
Ditto. This too would cause the thread to start running before
async_copy has been fully initialised.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2021-10-21 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 8:42 [PATCH] NFSD: Make use of the helper macro kthread_run() Cai Huoqing
2021-10-21 13:27 ` Trond Myklebust [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=b481c093912de062aee6ea456dcd6849e7515cbf.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bfields@fieldses.org \
--cc=caihuoqing@baidu.com \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.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