linux-hardening - Re: s390/defconfigs: set CONFIG_INIT_STACK

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-next>] [day] [month] [year] [list]

Message-ID: <ZG+rogQJO+U3kS4a@outflux.net>
Date:   Thu, 25 May 2023 11:40:34 -0700
From:   Kees Cook <kees@...flux.net>
To:     Heiko Carstens <hca@...ux.ibm.com>,
        Alexander Gordeev <agordeev@...ux.ibm.com>
Cc:     linux-hardening@...r.kernel.org
Subject: Re: s390/defconfigs: set CONFIG_INIT_STACK_NONE=y

Hi Heiko,

I had this[1] patch pointed out to me, but I couldn't find any discussion
about it on public lists. Can you give me some background on this? There
haven't been any general workloads identified where this has been
a problem, so I'm curious why this was seen as globally an issue on
s390. The expectation was to use __uninitialized on any variables where
this was noticed as a performance issue, and where the memory safety of
the variable could be proven. Turning it off by default seems like
rather too much, but perhaps there is something unique to s390 I don't
know about. :)

Thanks,

-Kees

[1] https://git.kernel.org/linus/124acbe275040809abfa5fbe6e25790a53d5a161

-- 
Kees Cook                                            @outflux.net