[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wihrtjjSsF6mGc7wjrtVQ-pha9ZAeo1rQAeuO1hr+i1qw@mail.gmail.com>
Date: Wed, 1 Apr 2020 13:55:11 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Adam Zabrocki <pi3@....com.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>, Jann Horn <jannh@...gle.com>,
Oleg Nesterov <oleg@...hat.com>, Andy Lutomirski <luto@...capital.net>,
Bernd Edlinger <bernd.edlinger@...mail.de>, Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>, stable <stable@...r.kernel.org>
Subject: Re: [PATCH] signal: Extend exec_id to 64bits
On Wed, Apr 1, 2020 at 1:50 PM Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
> I have updated the update of exec_id on exec to use WRITE_ONCE
> and the read of exec_id in do_notify_parent to use READ_ONCE
> to make it clear that there is no locking between these two
> locations.
Ack, makes sense to me.
Just put it in your branch, this doesn't look urgent, considering that
it's something that has been around forever.
Linus
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.
