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
| ||
|
Message-ID: <CAHk-=whjWyoognKy4QUUwf95L6qvPg7MGdp0CxqD2fpvZo7DLw@mail.gmail.com> Date: Sun, 17 Jul 2022 13:29:07 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Sudip Mukherjee <sudipm.mukherjee@...il.com> Cc: Michael Ellerman <mpe@...erman.id.au>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul Mackerras <paulus@...ba.org>, Kees Cook <keescook@...omium.org>, linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-kernel <linux-kernel@...r.kernel.org>, linux-hardening@...r.kernel.org, Segher Boessenkool <segher@...nel.crashing.org> Subject: Re: mainline build failure of powerpc allmodconfig for prom_init_check On Sun, Jul 17, 2022 at 1:25 PM Sudip Mukherjee <sudipm.mukherjee@...il.com> wrote: > > And the generated assembly still has the memset for "struct prom_args". Strange. That smells like a compiler bug to me. But I can't read powerpc assembly code - it's been too many years, and even back when I did read it I hated how the register "names" worked. Maybe it was never the args array, and it was about the other fields. Not that that makes any sense either, but it makes more sense than the compiler turning a series of volatile accesses into a memset. Linus
Powered by blists - more mailing lists