summaryrefslogtreecommitdiffstats
path: root/fs/btrfs
diff options
context:
space:
mode:
authorJohn Hubbard <jhubbard@nvidia.com>2019-07-30 22:46:27 -0700
committerThomas Gleixner <tglx@linutronix.de>2019-08-16 14:20:00 +0200
commita90118c445cc7f07781de26a9684d4ec58bfcfd1 (patch)
tree7e3ef3805ffe0a7c4ee8b038002e0c4b063dec1f /fs/btrfs
parent5ed1c835ed8b522ce25071cc2d56a9a09bd5b59e (diff)
downloadlinux-a90118c445cc7f07781de26a9684d4ec58bfcfd1.tar.bz2
x86/boot: Save fields explicitly, zero out everything else
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
Diffstat (limited to 'fs/btrfs')
0 files changed, 0 insertions, 0 deletions