From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>,
mpe@ellerman.id.au, benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, sam.bobroff@au1.ibm.com
Subject: Re: [PATCH 4/5] powerpc/tm: Check for already reclaimed tasks
Date: Mon, 16 Nov 2015 12:51:10 +0530 [thread overview]
Message-ID: <564983E6.6000307@linux.vnet.ibm.com> (raw)
In-Reply-To: <1447390652-28355-4-git-send-email-mikey@neuling.org>
On 11/13/2015 10:27 AM, Michael Neuling wrote:
> Currently we can hit a scenario where we'll tm_reclaim() twice. This
> results in a TM bad thing exception because the second reclaim occurs
> when not in suspend mode.
>
> The scenario in which this can happen is the following. We attempt to
> deliver a signal to userspace. To do this we need obtain the stack
> pointer to write the signal context. To get this stack pointer we
> must tm_reclaim() in case we need to use the checkpointed stack
> pointer (see get_tm_stackpointer()). Normally we'd then return
> directly to userspace to deliver the signal without going through
> __switch_to().
>
> Unfortunatley, if at this point we get an error (such as a bad
> userspace stack pointer), we need to exit the process. The exit will
> result in a __switch_to(). __switch_to() will attempt to save the
> process state which results in another tm_reclaim(). This
> tm_reclaim() now causes a TM Bad Thing exception as this state has
> already been saved and the processor is no longer in TM suspend mode.
> Whee!
>
> This patch checks the state of the MSR to ensure we are TM suspended
> before we attempt the tm_reclaim(). If we've already saved the state
> away, we should no longer be in TM suspend mode. This has the
> additional advantage of checking for a potential TM Bad Thing
> exception.
Can this situation be created using a test and verified that with
this new change, the kernel can handle it successfully. I guess
the self test in the series does not cover this scenario.
>
> Found using syscall fuzzer.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
> Cc: stable@vger.kernel.org
> ---
> arch/powerpc/kernel/process.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
> index 5fbe5d8..a1b41d1 100644
> --- a/arch/powerpc/kernel/process.c
> +++ b/arch/powerpc/kernel/process.c
> @@ -551,6 +551,25 @@ static void tm_reclaim_thread(struct thread_struct *thr,
> msr_diff &= MSR_FP | MSR_VEC | MSR_VSX | MSR_FE0 | MSR_FE1;
> }
>
> + /*
> + * Use the current MSR TM suspended bit to track if we have
> + * checkpointed state outstanding.
> + * On signal delivery, we'd normally reclaim the checkpointed
> + * state to obtain stack pointer (see:get_tm_stackpointer()).
> + * This will then directly return to userspace without going
> + * through __switch_to(). However, if the stack frame is bad,
> + * we need to exit this thread which calls __switch_to() which
> + * will again attempt to reclaim the already saved tm state.
> + * Hence we need to check that we've not already reclaimed
> + * this state.
> + * We do this using the current MSR, rather tracking it in
> + * some specific bit thread_struct bit, as it has the
There is one extra "bit" here ^^^^^.
next prev parent reply other threads:[~2015-11-16 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 4:57 [PATCH 1/5] powerpc: Print MSR TM bits in oops message Michael Neuling
2015-11-13 4:57 ` [PATCH 2/5] selftests/powerpc: Add TM signal return selftest Michael Neuling
2015-11-16 10:24 ` Michael Ellerman
2015-11-17 10:12 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 3/5] powerpc/tm: Block signal return setting invalid MSR state Michael Neuling
2015-11-16 10:05 ` Michael Ellerman
2015-11-17 10:30 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 4/5] powerpc/tm: Check for already reclaimed tasks Michael Neuling
2015-11-16 7:21 ` Anshuman Khandual [this message]
2015-11-16 9:23 ` Michael Neuling
2015-11-16 9:33 ` Michael Ellerman
2015-11-16 10:21 ` Michael Neuling
2015-11-13 4:57 ` [PATCH 5/5] powerpc/tm: Clarify get_tm_stackpointer() by renaming it Michael Neuling
2015-11-16 9:51 ` Michael Ellerman
2015-11-16 7:22 ` [PATCH 1/5] powerpc: Print MSR TM bits in oops message Anshuman Khandual
2015-11-16 9:27 ` Michael Ellerman
2015-11-16 22:07 ` Anton Blanchard
2015-11-17 10:01 ` Michael Neuling
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=564983E6.6000307@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sam.bobroff@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).