diff options
author | 2017-07-12 14:35:58 -0700 | |
---|---|---|
committer | 2017-07-12 16:26:02 -0700 | |
commit | e2ae8ab4b571e2e4094a28acb60649bc2732c67f (patch) | |
tree | 37ef8802e03e3e416be96534618a718833287d0e /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | efi: avoid fortify checks in EFI stub (diff) | |
download | linux-dev-e2ae8ab4b571e2e4094a28acb60649bc2732c67f.tar.xz linux-dev-e2ae8ab4b571e2e4094a28acb60649bc2732c67f.zip |
kexec_file: adjust declaration of kexec_purgatory
Defining kexec_purgatory as a zero-length char array upsets compile time
size checking. Since this is built on a per-arch basis, define it as an
unsized char array (like is done for other similar things, e.g. linker
sections). This silences the warning generated by the future
CONFIG_FORTIFY_SOURCE, which did not like the memcmp() of a "0 byte"
array. This drops the __weak and uses an extern instead, since both
users define kexec_purgatory.
Link: http://lkml.kernel.org/r/1497903987-21002-4-git-send-email-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Daniel Micay <danielmicay@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions