Re: Really enable -fstack-clash-protection on armhf/armel?
Julian Andres Klode <[email protected]>
| Newsgroups | gmane.linux.debian.ports.arm,gmane.linux.debian.devel.dpkg.general |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 23, 2023 at 10:45:33AM +0100, Matthias Klose wrote: > Hi, > > it looks like enabling this flag on armel/armhf is a little bit premature. > > Apparently it's not completely supported upstream, and might cause > regressions, according to > https://bugzilla.redhat.com/show_bug.cgi?id=1522678 > > Is that a feature that the Debian ARM32 porters and the security team really > want to support actively, despite the missing upstream support? > > In Ubuntu, people tracked down segfaults due to this change in at least > valgrind and gnutls, maybe more. It's 1.5 months later, valgrind is still failing and apt in valgrind hence segfaults. I am disabling the apt valgrind test on armhf in 2.7.8, but this situation is somewhat untenable. I did clone the bug to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060251 now.