linux-kernel - Re: [PATCH 19/19] x86, mpx: allow mixed binaries again

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 May 2015 23:55:44 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Dave Hansen <dave@...1.net>
cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	dave.hansen@...ux.intel.com
Subject: Re: [PATCH 19/19] x86, mpx: allow mixed binaries again

On Fri, 8 May 2015, Dave Hansen wrote:
> We explicitly disable allowing 32-bit binaries to enable
> MPX on 64-bit kernels.  Re-allow that.
> 
> Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>

> ---
> 
>  b/arch/x86/mm/mpx.c |    6 ------
>  1 file changed, 6 deletions(-)
> 
> diff -puN arch/x86/mm/mpx.c~x86-mpx-allow-mixed-binaries-again arch/x86/mm/mpx.c
> --- a/arch/x86/mm/mpx.c~x86-mpx-allow-mixed-binaries-again	2015-05-08 11:46:23.253134695 -0700
> +++ b/arch/x86/mm/mpx.c	2015-05-08 11:46:23.256134830 -0700
> @@ -368,12 +368,6 @@ static __user void *mpx_get_bounds_dir(v
>  		return MPX_INVALID_BOUNDS_DIR;
>  
>  	/*
> -	 * 32-bit binaries on 64-bit kernels are currently
> -	 * unsupported.
> -	 */
> -	if (IS_ENABLED(CONFIG_X86_64) && test_thread_flag(TIF_IA32))
> -		return MPX_INVALID_BOUNDS_DIR;
> -	/*
>  	 * The bounds directory pointer is stored in a register
>  	 * only accessible if we first do an xsave.
>  	 */
> _
> 
--
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/