Subject: Re: [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM

From: Sasha Levin <[email-masked]>
Date: Fri, 18 Jan 2019 09:51:21 -0500

On Thu, Jan 17, 2019 at 09:49:05AM -0200, Breno Leitao wrote:
>hi Sasha,
>
>On 1/16/19 11:35 AM, Sasha Levin wrote:
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a "Fixes:" tag,
>> fixing commit: e1c3743e1a20 powerpc/tm: Set MSR[TS] just prior to recheckpoint.
>>
>> The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93, v4.9.150.
>>
>> v4.20.2: Failed to apply! Possible dependencies:
>>     Unable to calculate
>>
>> v4.19.15: Failed to apply! Possible dependencies:
>>     Unable to calculate
>>
>> v4.14.93: Failed to apply! Possible dependencies:
>>     0d60619e1c0c ("powerpc: Add missing prototype for sys_debug_setcontext()")
>>     67b464a89c21 ("powerpc/32: Mark both tmp variables as unused")
>>     6f5b9f018f4c ("powerpc/tm: Unset MSR[TS] if not recheckpointing")
>>     b53875c4b4f2 ("powerpc: Add missing prototypes for sys_sigreturn() & sys_rt_sigreturn()")
>>     bf7fb32dd5fc ("powerpc: Add missing prototypes for ppc_select() & ppc_fadvise64_64()")
>>     f3675644e172 ("powerpc/syscalls: signal_{32, 64} - switch to SYSCALL_DEFINE")
>>
>> v4.9.150: Failed to apply! Possible dependencies:
>>     0d60619e1c0c ("powerpc: Add missing prototype for sys_debug_setcontext()")
>>     67b464a89c21 ("powerpc/32: Mark both tmp variables as unused")
>>     6f5b9f018f4c ("powerpc/tm: Unset MSR[TS] if not recheckpointing")
>>     b53875c4b4f2 ("powerpc: Add missing prototypes for sys_sigreturn() & sys_rt_sigreturn()")
>>     bf7fb32dd5fc ("powerpc: Add missing prototypes for ppc_select() & ppc_fadvise64_64()")
>>     f3675644e172 ("powerpc/syscalls: signal_{32, 64} - switch to SYSCALL_DEFINE")
>>
>>
>> How should we proceed with this patch?
>
>I understand that the commit that this patch fixes is not integrated into
>stable tree.
>
>I think it does not need to make stable at this moment, thus.

The commit it fixes (e1c3743e1a20) exists in all 4.9+ stable trees as it
itself was tagged for stable.

--
Thanks,
Sasha