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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 09:27:47 +0100
From:	Claudio Scordino <>
CC:	Catalin Marinas <>,,,
Subject: [PATCH][RE-SUBMIT] Default setting of the ARM_UNWIND option

Hi all,

          I didn't get any comment on this patch, so I try to re-submit.

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).

Having this option enabled by default, in fact, means that the kernel
does not boot if the user has a wrong compiler. If so, inspecting the
reason of the hang may require too much time (especially for people not
familiar with this option).

Consider that people may not know that their problem is related to the
ARM_UNWIND option. Therefore, they may waste time bisecting just to
understand where their problem really is.

If we disable this option by default, users who know the real meaning of
the option will still be able of setting it to the proper value.

Any comment ?

Many thanks,


View attachment "0001-Disable-stack-unwinding-support-by-default-since-it.patch" of type "text/x-patch" (1211 bytes)

Powered by blists - more mailing lists