linux-kernel - Re: [PATCH 2/5] x86, mpx: hook #BR exception handler to allocate bound tables

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:	Fri, 17 Jan 2014 09:30:45 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	Ren Qiaowei <qiaowei.ren@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] x86, mpx: hook #BR exception handler to allocate
 bound tables

On 01/17/2014 09:04 AM, Borislav Petkov wrote:
> On Fri, Jan 17, 2014 at 08:58:49AM -0800, H. Peter Anvin wrote:
>> #BR exception from kernel space -> panic.
>>
>> We have tons of rules on kernel code... e.g. no FPU usage.  This one is
>> minor in comparison.
> 
> So basically review should catch those wrong BOUND usages?
> 

Yes.  It would take some serious effort to get BOUND or MPX instructions
into the kernel -- you'd have to put them in inline assembly, and BOUND
doesn't even exist in 64-bit mode.

	-hpa

--
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/