From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Venkat <venkat88@linux.ibm.com>,
Thibault Ferrante <thibault.ferrante@canonical.com>
Cc: linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/powerpc/tm: Fix tcheck() reading uninitialised CR value
Date: Wed, 9 Sep 2026 10:56:49 +0200 [thread overview]
Message-ID: <d80d892c-8505-4530-a23f-e3b6daf72d03@kernel.org> (raw)
In-Reply-To: <4206CE63-979B-4464-BECE-F89D0B1BDC91@linux.ibm.com>
Le 09/09/2026 à 07:28, Venkat a écrit :
>
>
>> On 8 Sep 2026, at 3:24 AM, Thibault Ferrante <thibault.ferrante@canonical.com> wrote:
>>
>> tcheck() is used to check the current transaction state (active,
>> suspended, doomed) via the "tcheck" instruction, which writes its
>> result into CR field 0. The inline asm declared a GPR output operand
>> for this result but never actually moved the CR into it.
>>
>> Every caller (tcheck_doomed(), tcheck_active(), tcheck_suspended(),
>> tcheck_transactional()) has effectively been testing bits of an unrelated,
>> arbitrary register value since this helper was introduced.
>> The "& 4" mask discards the TDOOMED and TS_lsb (suspended) bits before
>> they ever reach the callers, so tcheck_doomed() and tcheck_suspended()
>> can never return true, and tcheck_transactional() degrades to being
>> equivalent to tcheck_active().
>>
>> Fix tcheck() to actually move CR into the output register with mfcr,
>> and widen the mask from "& 4" to "& 0xf" so the full CR0 nibble
>> (TDOOMED | TS_msb | TS_lsb | reserved) is preserved for the callers.
>>
>> This bug has been present since tcheck() was introduced.
>>
>> Link: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F2107442&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4805edfd01004fae88bf08df0e334066%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639245285430142903%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ho9uy5Jyj7SnKtiSZibCDfMR22FhBIuUSkgmguhENts%3D&reserved=0
>> Fixes: 8e03bd4e70b6 ("selftests/powerpc: Add TM tcheck helpers in C")
>> Signed-off-by: Thibault Ferrante <thibault.ferrante@canonical.com>
>> ---
>
>> tools/testing/selftests/powerpc/tm/tm.h | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/testing/selftests/powerpc/tm/tm.h b/tools/testing/selftests/powerpc/tm/tm.h
>> index c03c6e778876..6024ce4ba6ff 100644
>> --- a/tools/testing/selftests/powerpc/tm/tm.h
>> +++ b/tools/testing/selftests/powerpc/tm/tm.h
>> @@ -105,8 +105,12 @@ static inline bool failure_is_nesting(void)
>> static inline int tcheck(void)
>> {
>> long cr;
>> - asm volatile ("tcheck 0" : "=r"(cr) : : "cr0");
>> - return (cr >> 28) & 4;
>> + asm volatile("tcheck 0;"
Why not use cr7 instead of using cr0 and doing cr >> 28 below ?
>> + "mfcr %0;"
>> + : "=r"(cr)
>> + :
>> + : "cr0");
>> + return (cr >> 28) & 0xf;
>> }
>>
>> static inline bool tcheck_doomed(void)
>> --
>> 2.55.0
>>
>
next prev parent reply other threads:[~2026-09-09 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 21:54 Thibault Ferrante
2026-09-09 5:28 ` Venkat
2026-09-09 8:56 ` Christophe Leroy (CS GROUP) [this message]
2026-09-09 10:05 ` Thibault Ferrante
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=d80d892c-8505-4530-a23f-e3b6daf72d03@kernel.org \
--to=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shuah@kernel.org \
--cc=thibault.ferrante@canonical.com \
--cc=venkat88@linux.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
all inboxes | Powered by JetHome®