linux-kernel - Re: [PATCH 00/11] x86: Supervisor Mode Access Prevention

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, 21 Sep 2012 22:08:46 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Kees Cook <keescook@...omium.org>,
	Linda Wang <lwang@...hat.com>,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH 00/11] x86: Supervisor Mode Access Prevention


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Fri, Sep 21, 2012 at 12:43 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
>
> > Supervisor Mode Access Prevention (SMAP) is a new security 
> > feature disclosed by Intel in revision 014 of the Intel® 
> > Architecture Instruction Set Extensions Programming 
> > Reference:
> 
> Looks good.
> 
> Did this find any bugs, btw? We've had a few cases where we 
> forgot to use the proper user access function, and code just 
> happened to work because it all boils down to the same thing 
> and never got any page faults in practice anyway..

The 4g:4g patch sweeped out most of the historic ones - so what 
we have are perhaps newer bugs (but those should be pretty rare, 
most new features are cross-arch).

Thanks,

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