From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH] powerpc/tm: Fix more userspace r13 corruption
Date: Mon, 21 Mar 2022 16:05:52 +1100 [thread overview]
Message-ID: <164783915231.1783931.13421325090840249852.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220311024733.48926-1-npiggin@gmail.com>
On Fri, 11 Mar 2022 12:47:33 +1000, Nicholas Piggin wrote:
> Commit cf13435b730a ("powerpc/tm: Fix userspace r13 corruption") fixes
> a problem in treclaim where a SLB miss can occur on the
> thread_struct->ckpt_regs while SCRATCH0 is live with the saved user r13
> value, clobbering it with the kernel r13 and ultimately resulting in
> kernel r13 being stored in ckpt_regs.
>
> There is an equivalent problem in trechkpt where the user r13 value is
> loaded into r13 from chkpt_regs to be recheckpointed, but a SLB miss
> could occur on ckpt_regs accesses after that, which will result in r13
> being clobbered with a kernel value and that will get recheckpointed and
> then restored to user registers.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/tm: Fix more userspace r13 corruption
https://git.kernel.org/powerpc/c/9d71165d3934e607070c4e48458c0cf161b1baea
cheers
prev parent reply other threads:[~2022-03-21 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 2:47 [PATCH] powerpc/tm: Fix more userspace r13 corruption Nicholas Piggin
2022-03-11 3:59 ` Michael Neuling
2022-03-16 1:00 ` Michael Ellerman
2022-03-21 5:05 ` Michael Ellerman [this message]
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=164783915231.1783931.13421325090840249852.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.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 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.