linux-kernel - Re: [off-list] a path toward killing thread

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:	Sat, 18 Jun 2016 09:23:19 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	"H. Peter Anvin" <hpa@...or.com>,
	Al Viro <viro@...IV.linux.org.uk>,
	Andy Lutomirski <luto@...capital.net>
Cc:	Kees Cook <keescook@...omium.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [off-list] a path toward killing thread_info

On Fri, 2016-06-17 at 16:10 -0700, H. Peter Anvin wrote:
> 
> Yes.
> 
> I did a half-finished patchset to do this once, in that I defined
> accessor functions which used container_of instead of pointers on
> architectures where this merge was enabled.

How do you get to "current" in that case ? A normal per-cpu ?

Cheers,
Ben.