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]

Message-ID: <20160617230431.GG14480@ZenIV.linux.org.uk>
Date:	Sat, 18 Jun 2016 00:04:31 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Kees Cook <keescook@...omium.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	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, Jun 17, 2016 at 03:41:49PM -0700, Andy Lutomirski wrote:

> PeterZ, I'm thinking of adding task_ti_flags_ptr to directly find the
> ti flags word given a task_struct * so the scheduler can use it.  Does
> that seem reasonable to you?

What are you trying to do?  Merge task_struct and thread_info?