From ce437484fced8292d90497d7b740335428fffed6 Mon Sep 17 00:00:00 2001 From: LemonBoy Date: Thu, 5 Nov 2020 16:52:51 +0100 Subject: linux-user: Correct definition of stack_t Some platforms used the wrong definition of stack_t where the flags and size fields were swapped or where the flags field had type ulong instead of int. Due to the presence of padding space in the structure and the prevalence of little-endian machines this problem went unnoticed for a long time. The type definitions have been cross-checked with the ones defined in the Linux kernel v5.9, plus some older versions for a few architecture that have been removed and Xilinx's kernel fork for NiosII [1]. The bsd-user headers remain unchanged as I don't know if they are wrong or not. [1] https://github.com/Xilinx/linux-xlnx/blob/master/arch/nios2/include/uapi/asm/signal.h Signed-off-by: Giuseppe Musacchio Reviewed-by: Peter Maydell Message-Id: Signed-off-by: Laurent Vivier --- linux-user/hppa/target_signal.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'linux-user/hppa') diff --git a/linux-user/hppa/target_signal.h b/linux-user/hppa/target_signal.h index c2a0102..c52a3ea 100644 --- a/linux-user/hppa/target_signal.h +++ b/linux-user/hppa/target_signal.h @@ -44,7 +44,7 @@ typedef struct target_sigaltstack { abi_ulong ss_sp; - int32_t ss_flags; + abi_int ss_flags; abi_ulong ss_size; } target_stack_t; -- cgit v1.1