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] [day] [month] [year] [list]

Message-ID: <AD01F419-AC5D-4BF6-8C38-781EFBEC206F@zytor.com>
Date:	Fri, 17 Jun 2016 17:02:00 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	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 June 17, 2016 4:23:19 PM PDT, Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
>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.

Yes.  We already do that on x86-64 at least.
-- 
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.