Re: [PATCH v2 1/5] exec: Only compute current once in flush_old_exec

From: Christian Brauner
Date: Tue Mar 10 2020 - 17:13:25 EST

Next message: Jeff Layton: "Re: [locks] 6d390e4b5d: will-it-scale.per_process_ops -96.6% regression"
Previous message: Eric W. Biederman: "Re: [PATCH v2 4/5] exec: Move exec_mmap right after de_thread in flush_old_exec"
In reply to: Kees Cook: "Re: [PATCH v2 1/5] exec: Only compute current once in flush_old_exec"
Next in thread: Eric W. Biederman: "[PATCH v2 2/5] exec: Factor unshare_sighand out of de_thread and call it separately"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, Mar 08, 2020 at 04:35:26PM -0500, Eric W. Biederman wrote:
>
> Make it clear that current only needs to be computed once in
> flush_old_exec. This may have some efficiency improvements and it
> makes the code easier to change.
>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>

Acked-by: Christian Brauner <christian.brauner@xxxxxxxxxx>

Next message: Jeff Layton: "Re: [locks] 6d390e4b5d: will-it-scale.per_process_ops -96.6% regression"
Previous message: Eric W. Biederman: "Re: [PATCH v2 4/5] exec: Move exec_mmap right after de_thread in flush_old_exec"
In reply to: Kees Cook: "Re: [PATCH v2 1/5] exec: Only compute current once in flush_old_exec"
Next in thread: Eric W. Biederman: "[PATCH v2 2/5] exec: Factor unshare_sighand out of de_thread and call it separately"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]