linux-kernel - Re: [patch 2/2] c/r: prctl: Add ability to get clear_tid

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: <20120319165534.GI19594@moon>
Date:	Mon, 19 Mar 2012 20:55:34 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	Kees Cook <keescook@...omium.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Pavel Emelyanov <xemul@...allels.com>,
	Tejun Heo <tj@...nel.org>, Matt Helsley <matthltc@...ibm.com>,
	Andrew Vagin <avagin@...nvz.org>,
	Pedro Alves <palves@...hat.com>
Subject: Re: [patch 2/2] c/r: prctl: Add ability to get clear_tid_address

On Mon, Mar 19, 2012 at 09:51:36AM -0700, Kees Cook wrote:
> On Fri, Mar 16, 2012 at 1:55 PM, Cyrill Gorcunov <gorcunov@...nvz.org> wrote:
> > Zero is written at clear_tid_address, when
> > the process exits. This functionality is used
> > by pthread_join().
> >
> > We already have sys_set_tid_address() to change this
> > address for current task but there is no way to obtain
> > it from a user space.
> 
> Is it worth introducing a syscall for this just for symmetry? I
> suspect not, in which case:
> 
> Acked-by: Kees Cook <keescook@...omium.org>
> 

Thanks Kees! syscall was considered as "no-no" in previous
convesation about this patch, so we switched to prctl.

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