Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 1 Apr 2020 19:05:59 -0700
From: Linus Torvalds <>
To: Jann Horn <>
Cc: "Eric W. Biederman" <>, Alan Stern <>, 
	Andrea Parri <>, Will Deacon <>, 
	Peter Zijlstra <>, Boqun Feng <>, 
	Nicholas Piggin <>, David Howells <>, 
	Jade Alglave <>, Luc Maranget <>, 
	"Paul E. McKenney" <>, Akira Yokosawa <>, 
	Daniel Lustig <>, Adam Zabrocki <>, 
	kernel list <>, 
	Kernel Hardening <>, Oleg Nesterov <>, 
	Andy Lutomirski <>, Bernd Edlinger <>, 
	Kees Cook <>, Andrew Morton <>, 
	stable <>, Marco Elver <>, 
	Dmitry Vyukov <>, kasan-dev <>
Subject: Re: [PATCH] signal: Extend exec_id to 64bits

On Wed, Apr 1, 2020 at 6:36 PM Jann Horn <> wrote:
> Since the read is already protected by the tasklist_lock, an
> alternative might be to let the execve path also take that lock to
> protect the sequence number update,


tasklist_lock is aboue the hottest lock there is in all of the kernel.

We're not doing stupid things for theoretical issues.

Stop this crazy argument.

A comment - sure. 64-bit atomics or very expensive locks? Not a chance.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.