linux-kernel - Re: stackinit unit test failures on m68k

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87y1b5zfis.fsf@igel.home>
Date: Tue, 27 Feb 2024 23:52:27 +0100
From: Andreas Schwab <schwab@...ux-m68k.org>
To: Kees Cook <keescook@...omium.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,  Guenter Roeck
 <linux@...ck-us.net>,  linux-m68k@...ts.linux-m68k.org,
  linux-kernel@...r.kernel.org
Subject: Re: stackinit unit test failures on m68k

On Feb 27 2024, Kees Cook wrote:

> Oh, no, that wasn't it. Something else is happening. The stack pointer
> isn't moving between them. Is there anything special about character
> arrays on m68k?

You mean, beyond undefined behaviour?

-- 
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."