aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/fs/binfmt_flat.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2019-06-13 09:08:55 +0200
committerGreg Ungerer <gerg@kernel.org>2019-06-24 09:16:47 +1000
commit34b4664ac4824d6c7a8b29db24b18733df07b2f4 (patch)
treeb94e0eccb77f806991a97477d09f30ff2ba91b1b /fs/binfmt_flat.c
parentbinfmt_flat: consolidate two version of flat_v2_reloc_t (diff)
downloadwireguard-linux-34b4664ac4824d6c7a8b29db24b18733df07b2f4.tar.xz
wireguard-linux-34b4664ac4824d6c7a8b29db24b18733df07b2f4.zip
binfmt_flat: use fixed size type for the on-disk format
So far binfmt_flat has only been supported on 32-bit platforms, so the variable size of the fields didn't matter. But the upcoming RISC-V nommu port supports 64-bit CPUs, and we now have a conflict between the elf2flt creation tool that always uses 32-bit fields and the kernel that uses (unsigned) long field. Switch to the userspace view as the rest of the binfmt_flat format is completely architecture neutral, and binfmt_flat isn't the right binary format for huge executables to start with. While we're at it also ensure these fields are using __be types as they big endian and are byte swapped when loaded. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Vladimir Murzin <vladimir.murzin@arm.com> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
Diffstat (limited to 'fs/binfmt_flat.c')
0 files changed, 0 insertions, 0 deletions