From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, Russell Currey <ruscur@russell.cc>
Subject: Re: [PATCH] powerpc/security: Use a mutex for interrupt exit code patching
Date: Thu, 28 Oct 2021 13:03:24 +1000 [thread overview]
Message-ID: <1635390156.m54wv9anx4.astroid@bobo.none> (raw)
In-Reply-To: <20211027072410.40950-1-ruscur@russell.cc>
Excerpts from Russell Currey's message of October 27, 2021 5:24 pm:
> The mitigation-patching.sh script in the powerpc selftests toggles
> all mitigations on and off simultaneously, revealing that rfi_flush
> and stf_barrier cannot safely operate at the same time due to races
> in updating the static key.
>
> On some systems, the static key code throws a warning and the kernel
> remains functional. On others, the kernel will hang or crash.
>
> Fix this by slapping on a mutex.
>
> Fixes: 13799748b957 ("powerpc/64: use interrupt restart table to speed up return from interrupt")
> Signed-off-by: Russell Currey <ruscur@russell.cc>
Doh,
Acked-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> arch/powerpc/lib/feature-fixups.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/powerpc/lib/feature-fixups.c b/arch/powerpc/lib/feature-fixups.c
> index cda17bee5afe..9956277fbd88 100644
> --- a/arch/powerpc/lib/feature-fixups.c
> +++ b/arch/powerpc/lib/feature-fixups.c
> @@ -228,6 +228,7 @@ static void do_stf_exit_barrier_fixups(enum stf_barrier_type types)
>
> static bool stf_exit_reentrant = false;
> static bool rfi_exit_reentrant = false;
> +static DEFINE_MUTEX(exit_flush_lock);
>
> static int __do_stf_barrier_fixups(void *data)
> {
> @@ -253,6 +254,9 @@ void do_stf_barrier_fixups(enum stf_barrier_type types)
> * low level interrupt exit code before patching. After the patching,
> * if allowed, then flip the branch to allow fast exits.
> */
> +
> + // Prevent static key update races with do_rfi_flush_fixups()
> + mutex_lock(&exit_flush_lock);
> static_branch_enable(&interrupt_exit_not_reentrant);
>
> stop_machine(__do_stf_barrier_fixups, &types, NULL);
> @@ -264,6 +268,7 @@ void do_stf_barrier_fixups(enum stf_barrier_type types)
>
> if (stf_exit_reentrant && rfi_exit_reentrant)
> static_branch_disable(&interrupt_exit_not_reentrant);
> + mutex_unlock(&exit_flush_lock);
> }
>
> void do_uaccess_flush_fixups(enum l1d_flush_type types)
> @@ -486,6 +491,9 @@ void do_rfi_flush_fixups(enum l1d_flush_type types)
> * without stop_machine, so this could be achieved with a broadcast
> * IPI instead, but this matches the stf sequence.
> */
> +
> + // Prevent static key update races with do_stf_barrier_fixups()
> + mutex_lock(&exit_flush_lock);
> static_branch_enable(&interrupt_exit_not_reentrant);
>
> stop_machine(__do_rfi_flush_fixups, &types, NULL);
> @@ -497,6 +505,7 @@ void do_rfi_flush_fixups(enum l1d_flush_type types)
>
> if (stf_exit_reentrant && rfi_exit_reentrant)
> static_branch_disable(&interrupt_exit_not_reentrant);
> + mutex_unlock(&exit_flush_lock);
> }
>
> void do_barrier_nospec_fixups_range(bool enable, void *fixup_start, void *fixup_end)
> --
> 2.33.1
>
>
next prev parent reply other threads:[~2021-10-28 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 7:24 [PATCH] powerpc/security: Use a mutex for interrupt exit code patching Russell Currey
2021-10-28 3:03 ` Nicholas Piggin [this message]
2021-11-02 10:12 ` Michael Ellerman
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=1635390156.m54wv9anx4.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ruscur@russell.cc \
/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