From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"Olga Kornievskaia <okorniev@redhat.com> Olga Kornievskaia"
<kolga@netapp.com>, Dai Ngo <dai.ngo@oracle.com>,
Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH nfsd-next] SQUASH sunrpc: allow svc threads to fail initialisation cleanly
Date: Sun, 15 Sep 2024 20:24:48 -0400 [thread overview]
Message-ID: <1ada154324d020a86aff7a7f4d155c13227abc7d.camel@kernel.org> (raw)
In-Reply-To: <172644394073.17050.16376953609629336068@noble.neil.brown.name>
On Mon, 2024-09-16 at 09:45 +1000, NeilBrown wrote:
> The memory barriers in this patch were all wrong.
> smp_store_release / smp_load_acquire ensures that all changes written
> before the store_release are equally visible after the acquire.
> These are not needed here as the *only* value that
> svc_thread_init_status() or its caller sets that is of any interest to
> svc_start_kthread() is ->rq_err. The barrier wold effect writes before
> ->rq_err is written and reads after ->rq_err is read.
>
> However we DO need a full memory barrier between setting ->rq_err and
> before the the waitqueue_active() read in wake_up_var(). This is a
> barrier between a write and a read, hence a full barrier: smb_mb().
>
> This addresses a race if wait_var_event() adds itself to the wait queue
> and tests ->rq_err such that the read in waitqueue_active() happens
> earlier and doesn't see that the task has been added, and the ->rq_err
> write is delayed so that the waiting task doesn't see it. In this case
> the wake_up never happens.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
> ---
> include/linux/sunrpc/svc.h | 7 +++++--
> net/sunrpc/svc.c | 3 +--
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/sunrpc/svc.h b/include/linux/sunrpc/svc.h
> index 437672bcaa22..558e5ae03103 100644
> --- a/include/linux/sunrpc/svc.h
> +++ b/include/linux/sunrpc/svc.h
> @@ -326,8 +326,11 @@ static inline bool svc_thread_should_stop(struct svc_rqst *rqstp)
> */
> static inline void svc_thread_init_status(struct svc_rqst *rqstp, int err)
> {
> - /* store_release ensures svc_start_kthreads() sees the error */
> - smp_store_release(&rqstp->rq_err, err);
> + rqstp->rq_err = err;
> + /* memory barrier ensures assignment to error above is visible before
> + * waitqueue_active() test below completes.
> + */
> + smb_mb();
> wake_up_var(&rqstp->rq_err);
> if (err)
> kthread_exit(1);
> diff --git a/net/sunrpc/svc.c b/net/sunrpc/svc.c
> index ff6f3e35b36d..9aff845196ce 100644
> --- a/net/sunrpc/svc.c
> +++ b/net/sunrpc/svc.c
> @@ -818,8 +818,7 @@ svc_start_kthreads(struct svc_serv *serv, struct svc_pool *pool, int nrservs)
> svc_sock_update_bufs(serv);
> wake_up_process(task);
>
> - /* load_acquire ensures we get value stored in svc_thread_init_status() */
> - wait_var_event(&rqstp->rq_err, smp_load_acquire(&rqstp->rq_err) != -EAGAIN);
> + wait_var_event(&rqstp->rq_err, rqstp->rq_err != -EAGAIN);
> err = rqstp->rq_err;
> if (err) {
> svc_exit_thread(rqstp);
Makes sense.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-09-16 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 23:45 [PATCH nfsd-next] SQUASH sunrpc: allow svc threads to fail initialisation cleanly NeilBrown
2024-09-16 0:24 ` Jeff Layton [this message]
2024-09-16 3:50 ` Chuck Lever
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=1ada154324d020a86aff7a7f4d155c13227abc7d.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.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