summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2020-10-04 19:57:20 -0700
committerKees Cook <keescook@chromium.org>2020-10-27 11:13:41 -0700
commit3e6631485fae70f474d5bd85cfaf0f113f61ccce (patch)
tree926ee0a90d438cc02f6a006fd22553a607c62f6c /crypto
parent3650b228f83adda7e5ee532e2b90429c03f7b9ec (diff)
downloadlinux-3e6631485fae70f474d5bd85cfaf0f113f61ccce.tar.gz
linux-3e6631485fae70f474d5bd85cfaf0f113f61ccce.tar.bz2
linux-3e6631485fae70f474d5bd85cfaf0f113f61ccce.zip
vmlinux.lds.h: Keep .ctors.* with .ctors
Under some circumstances, the compiler generates .ctors.* sections. This is seen doing a cross compile of x86_64 from a powerpc64el host: x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_clock.o' being placed in section `.ctors.65435' x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ftrace.o' being placed in section `.ctors.65435' x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ring_buffer.o' being placed in section `.ctors.65435' Include these orphans along with the regular .ctors section. Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Tested-by: Stephen Rothwell <sfr@canb.auug.org.au> Fixes: 83109d5d5fba ("x86/build: Warn on orphan section placement") Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Nick Desaulniers <ndesaulniers@google.com> Link: https://lore.kernel.org/r/20201005025720.2599682-1-keescook@chromium.org
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions