summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJohn Hubbard <jhubbard@nvidia.com>2019-07-30 22:46:27 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-09-06 10:18:10 +0200
commit41664b97f46e2c951c05313f4a9e9bb1fecc1439 (patch)
tree4a3ebba764e4a04b75a7c1f3a8046df15caa05a4 /tools/perf/scripts/python
parenta0a0e3bf98fc3c0f13b669ea2a66995d677a2484 (diff)
x86/boot: Save fields explicitly, zero out everything else
commit a90118c445cc7f07781de26a9684d4ec58bfcfd1 upstream. Recent gcc compilers (gcc 9.1) generate warnings about an out of bounds memset, if the memset goes accross several fields of a struct. This generated a couple of warnings on x86_64 builds in sanitize_boot_params(). Fix this by explicitly saving the fields in struct boot_params that are intended to be preserved, and zeroing all the rest. [ tglx: Tagged for stable as it breaks the warning free build there as well ] Suggested-by: Thomas Gleixner <tglx@linutronix.de> Suggested-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: John Hubbard <jhubbard@nvidia.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/20190731054627.5627-2-jhubbard@nvidia.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions