linux-kernel - Re: [PATCH 03/19] x86, mpx: Use new get_xsave_field

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]

Message-ID: <alpine.DEB.2.11.1505191015580.4225@nanos>
Date:	Tue, 19 May 2015 10:16:12 +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, oleg@...hat.com, bp@...en8.de,
	riel@...hat.com, sbsiddha@...il.com, luto@...capital.net,
	mingo@...hat.com, hpa@...or.com, fenghua.yu@...el.com
Subject: Re: [PATCH 03/19] x86, mpx: Use new get_xsave_field_ptr()

On Mon, 18 May 2015, Dave Hansen wrote:
> From: Dave Hansen <dave.hansen@...ux.intel.com>
> 
> The MPX registers (bndcsr/bndcfgu/bndstatus) are not directly
> accessible via normal instructions.  They essentially act as
> if they were floating point registers and are saved/restored
> along with those registers.
> 
> There are two main paths in the MPX code where we care about
> the contents of these registers:
> 	1. #BR (bounds) faults
> 	2. the prctl() code where we are setting MPX up
> 
> Both of those paths _might_ be called without the FPU having
> been used.  That means that 'tsk->thread.fpu.state' might
> never be allocated.
> 
> Also, fpu_save_init() is not preempt-safe.  It was a bug to
> call it without disabling preemption.  The new
> get_xsave_addr() calls unlazy_fpu() instead and properly
> disables preemption.
> 
> Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
--
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/