lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 2 Sep 2015 22:34:53 +0300
From:	Mikko Rapeli <mikko.rapeli@....fi>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 94/98] HACK arch/x86/include/uapi/asm/sigcontext32.h:
 remove _fpx_sw_bytes from union

Hi Ingo, Thomas and Peter,

Do you have any pointers for me how arch/x86/include/uapi/asm/sigcontext32.h
could be fixed to also compile in userspace? Is definition of _fpx_sw_bytes
or _fpstate_ia32 even needed there?

Instructions to reproduce the userspace build failure are here:
https://lkml.org/lkml/2015/5/30/98

-Mikko

On Sat, May 30, 2015 at 05:39:26PM +0200, Mikko Rapeli wrote:
> I have no idea what I'm doing but this fixes header file compilation in
> userspace:
> 
> error: field ‘sw_reserved’ has incomplete type
>    struct _fpx_sw_bytes sw_reserved;
> 
> Signed-off-by: Mikko Rapeli <mikko.rapeli@....fi>
> ---
>  arch/x86/include/uapi/asm/sigcontext32.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/x86/include/uapi/asm/sigcontext32.h b/arch/x86/include/uapi/asm/sigcontext32.h
> index ad1478c..ceaaa78 100644
> --- a/arch/x86/include/uapi/asm/sigcontext32.h
> +++ b/arch/x86/include/uapi/asm/sigcontext32.h
> @@ -45,7 +45,6 @@ struct _fpstate_ia32 {
>  	__u32	padding[44];
>  	union {
>  		__u32 padding2[12];
> -		struct _fpx_sw_bytes sw_reserved;
>  	};
>  };
>  
> -- 
> 2.1.4
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ