From: Waiman Long <waiman.long@hpe.com>
To: Jason Low <jason.low2@hpe.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Terry Rudd <terry.rudd@hpe.com>,
Scott J Norton <scott.norton@hpe.com>,
Jason Low <jason.low2@hp.com>
Subject: Re: [PATCH v2] locking/mutex: Set and clear owner using WRITE_ONCE()
Date: Fri, 20 May 2016 19:01:43 -0400 [thread overview]
Message-ID: <573F9757.9020805@hpe.com> (raw)
In-Reply-To: <1463782776.2479.9.camel@j-VirtualBox>
On 05/20/2016 06:19 PM, Jason Low wrote:
> The mutex owner can get read and written to locklessly.
> Use WRITE_ONCE when setting and clearing the owner field
> in order to avoid optimizations such as store tearing. This
> avoids situations where the owner field gets written to with
> multiple stores and another thread could concurrently read
> and use a partially written owner value.
>
> Signed-off-by: Jason Low<jason.low2@hpe.com>
> Acked-by: Davidlohr Bueso<dave@stgolabs.net>
> ---
> kernel/locking/mutex-debug.h | 4 ++--
> kernel/locking/mutex.h | 10 ++++++++--
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/locking/mutex-debug.h b/kernel/locking/mutex-debug.h
> index 0799fd3..372e653 100644
> --- a/kernel/locking/mutex-debug.h
> +++ b/kernel/locking/mutex-debug.h
> @@ -29,12 +29,12 @@ extern void debug_mutex_init(struct mutex *lock, const char *name,
>
> static inline void mutex_set_owner(struct mutex *lock)
> {
> - lock->owner = current;
> + WRITE_ONCE(lock->owner, current);
> }
>
> static inline void mutex_clear_owner(struct mutex *lock)
> {
> - lock->owner = NULL;
> + WRITE_ONCE(lock->owner, NULL);
> }
>
> #define spin_lock_mutex(lock, flags) \
> diff --git a/kernel/locking/mutex.h b/kernel/locking/mutex.h
> index 5cda397..12f9619 100644
> --- a/kernel/locking/mutex.h
> +++ b/kernel/locking/mutex.h
> @@ -17,14 +17,20 @@
> __list_del((waiter)->list.prev, (waiter)->list.next)
>
> #ifdef CONFIG_MUTEX_SPIN_ON_OWNER
> +/*
> + * The mutex owner can get read and written to locklessly.
> + * We should use WRITE_ONCE when writing the owner value to
> + * avoid store tearing, otherwise, a thread could potentially
> + * read a partially written and incomplete owner value.
> + */
> static inline void mutex_set_owner(struct mutex *lock)
> {
> - lock->owner = current;
> + WRITE_ONCE(lock->owner, current);
> }
>
> static inline void mutex_clear_owner(struct mutex *lock)
> {
> - lock->owner = NULL;
> + WRITE_ONCE(lock->owner, NULL);
> }
> #else
> static inline void mutex_set_owner(struct mutex *lock)
Acked-by: Waiman Long <Waiman.Long@hpe.com>
next prev parent reply other threads:[~2016-05-20 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 22:19 [PATCH v2] locking/mutex: Set and clear owner using WRITE_ONCE() Jason Low
2016-05-20 23:01 ` Waiman Long [this message]
2016-06-03 10:57 ` [tip:locking/core] " tip-bot for Jason Low
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=573F9757.9020805@hpe.com \
--to=waiman.long@hpe.com \
--cc=dave@stgolabs.net \
--cc=jason.low2@hp.com \
--cc=jason.low2@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hpe.com \
--cc=terry.rudd@hpe.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