From: Peter Zijlstra <peterz@infradead.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH v2 0/2] locking: Fix racy reads of owner->on_cpu
Date: Fri, 3 Dec 2021 09:33:14 +0100 [thread overview]
Message-ID: <YanWSh2miL6E+aZR@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211203075935.136808-1-wangkefeng.wang@huawei.com>
On Fri, Dec 03, 2021 at 03:59:33PM +0800, Kefeng Wang wrote:
> v2:
> - adding owner_on_cpu() refactor, shared by mutex/rtmutex/rwsem
>
> v1: https://lore.kernel.org/all/20211202101238.33546-1-elver@google.com/
>
> Kefeng Wang (1):
> locking: Make owner_on_cpu() into <linux/sched.h>
>
> Marco Elver (1):
> locking: Mark racy reads of owner->on_cpu
>
> include/linux/sched.h | 9 +++++++++
> kernel/locking/mutex.c | 11 ++---------
> kernel/locking/rtmutex.c | 5 ++---
> kernel/locking/rwsem.c | 9 ---------
> 4 files changed, 13 insertions(+), 21 deletions(-)
Thanks!
next prev parent reply other threads:[~2021-12-03 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:59 [PATCH v2 0/2] locking: Fix racy reads of owner->on_cpu Kefeng Wang
2021-12-03 7:59 ` [PATCH v2 1/2] locking: Make owner_on_cpu() into <linux/sched.h> Kefeng Wang
2021-12-06 15:15 ` [tip: locking/core] " tip-bot2 for Kefeng Wang
2021-12-03 7:59 ` [PATCH v2 2/2] locking: Mark racy reads of owner->on_cpu Kefeng Wang
2021-12-06 15:15 ` [tip: locking/core] " tip-bot2 for Marco Elver
2021-12-03 8:33 ` Peter Zijlstra [this message]
2021-12-03 15:49 ` [PATCH v2 0/2] locking: Fix " Waiman Long
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=YanWSh2miL6E+aZR@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=will@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