| 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: <1256555452.5282.21.camel@pc1117.cambridge.arm.com> Date: Mon, 26 Oct 2009 11:10:52 +0000 From: Catalin Marinas <catalin.marinas@....com> To: Claudio Scordino <claudio@...dence.eu.com> Cc: linux-kernel@...r.kernel.org, rmk+kernel@....linux.org.uk, linux-arm-kernel@...ts.arm.linux.org.uk, akpm@...ux-foundation.org Subject: Re: [PATCH][RE-SUBMIT] Default setting of the ARM_UNWIND option On Mon, 2009-10-26 at 09:27 +0100, Claudio Scordino wrote: > My ARM board hanged at the initial "Calibrating delay loop" message. > > After some inspection, I found out the problem to be with commit > adf8b37bafc1495393201a2ae4235846371870d0. This commit introduces stack > unwinding for ARM, and set it enabled by default. However, it seems to > not work with buggy or not-EABI compilers. > > My suggestion is to keep the feature (which is fine) but change the > default setting of the option (see the attached patch). The option still depends on EXPERIMENTAL, so you get ARM_UNWIND on when enabling that. I'm more in favour of a #warning on #error in the unwind.c file based on the compiler version rather than not having it on by default. The reason is that people reported performance improvements when compiling the kernel without frame pointers. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists