From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86 <x86@kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Anton Blanchard <anton@ozlabs.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] membarrier: Explicitly sync remote cores when SYNC_CORE is requested
Date: Wed, 2 Dec 2020 14:43:32 -0500 (EST) [thread overview]
Message-ID: <1515215436.71.1606938212130.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <6d4c8ff7300c72fd4d44ee5755bd149359f2661a.1606923183.git.luto@kernel.org>
----- On Dec 2, 2020, at 10:35 AM, Andy Lutomirski luto@kernel.org wrote:
> membarrier() does not explicitly sync_core() remote CPUs; instead, it
> relies on the assumption that an IPI will result in a core sync. On
> x86, I think this may be true in practice, but it's not architecturally
> reliable. In particular, the SDM and APM do not appear to guarantee
> that interrupt delivery is serializing. While IRET does serialize, IPI
> return can schedule, thereby switching to another task in the same mm
> that was sleeping in a syscall. The new task could then SYSRET back to
> usermode without ever executing IRET.
>
> Make this more robust by explicitly calling sync_core_before_usermode()
> on remote cores. (This also helps people who search the kernel tree for
> instances of sync_core() and sync_core_before_usermode() -- one might be
> surprised that the core membarrier code doesn't currently show up in a
> such a search.)
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> ---
> kernel/sched/membarrier.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/kernel/sched/membarrier.c b/kernel/sched/membarrier.c
> index 6251d3d12abe..01538b31f27e 100644
> --- a/kernel/sched/membarrier.c
> +++ b/kernel/sched/membarrier.c
> @@ -166,6 +166,23 @@ static void ipi_mb(void *info)
> smp_mb(); /* IPIs should be serializing but paranoid. */
> }
>
> +static void ipi_sync_core(void *info)
> +{
> + /*
> + * The smp_mb() in membarrier after all the IPIs is supposed to
> + * ensure that memory on remote CPUs that occur before the IPI
> + * become visible to membarrier()'s caller -- see scenario B in
> + * the big comment at the top of this file.
> + *
> + * A sync_core() would provide this guarantee, but
> + * sync_core_before_usermode() might end up being deferred until
> + * after membarrier()'s smp_mb().
> + */
> + smp_mb(); /* IPIs should be serializing but paranoid. */
> +
> + sync_core_before_usermode();
> +}
> +
> static void ipi_rseq(void *info)
> {
> /*
> @@ -301,6 +318,7 @@ static int membarrier_private_expedited(int flags, int
> cpu_id)
> if (!(atomic_read(&mm->membarrier_state) &
> MEMBARRIER_STATE_PRIVATE_EXPEDITED_SYNC_CORE_READY))
> return -EPERM;
> + ipi_func = ipi_sync_core;
> } else if (flags == MEMBARRIER_FLAG_RSEQ) {
> if (!IS_ENABLED(CONFIG_RSEQ))
> return -EINVAL;
> --
> 2.28.0
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2020-12-02 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:35 [PATCH v2 0/4] membarrier fixes Andy Lutomirski
2020-12-02 15:35 ` [PATCH v2 1/4] x86/membarrier: Get rid of a dubious optimization Andy Lutomirski
2020-12-02 15:35 ` [PATCH v2 2/4] membarrier: Add an actual barrier before rseq_preempt() Andy Lutomirski
2020-12-02 19:40 ` Mathieu Desnoyers
2020-12-02 15:35 ` [PATCH v2 3/4] membarrier: Explicitly sync remote cores when SYNC_CORE is requested Andy Lutomirski
2020-12-02 19:43 ` Mathieu Desnoyers [this message]
2020-12-02 15:35 ` [PATCH v2 4/4] membarrier: Execute SYNC_CORE on the calling thread Andy Lutomirski
2020-12-02 19:39 ` Mathieu Desnoyers
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=1515215436.71.1606938212130.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=anton@ozlabs.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=npiggin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.