Issue metadata
Sign in to add a comment
|
mosys binary has executable stack markings |
||||||||||||||||||||||
Issue descriptionhttp://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=193607308 Generally this happens if assembly files are not tagged correctly. https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart Adding this this to end of assembly file should generally fix the problem for assembly files. #if defined(__linux__) && defined(__ELF__) .section .note.GNU-stack,"",%progbits #endif If mosys does need executable stack, please let us know so that we can filter it.
,
Apr 25 2018
,
Apr 27 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/mosys/+/0a2e82b912985764450ced09dd5bdd2ca2a546f4 commit 0a2e82b912985764450ced09dd5bdd2ca2a546f4 Author: C Shapiro <shapiroc@chromium.org> Date: Fri Apr 27 04:10:07 2018 mosys: Remove executable stack markings BUG= chromium:835378 TEST=emerge-reef and local test Change-Id: I41b5931ec36a3f5d15ca71ec220cd76e372fcdca Reviewed-on: https://chromium-review.googlesource.com/1029008 Commit-Ready: C Shapiro <shapiroc@google.com> Tested-by: C Shapiro <shapiroc@google.com> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> [modify] https://crrev.com/0a2e82b912985764450ced09dd5bdd2ca2a546f4/lib/cros_config/config.dtb.S
,
Apr 27 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manojgupta@chromium.org
, Apr 25 2018