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  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]
Date:   Fri, 8 May 2020 22:33:51 -0700
From:   Kees Cook <>
To:     "Eric W. Biederman" <>
        Linus Torvalds <>,
        Oleg Nesterov <>, Jann Horn <>,
        Greg Ungerer <>,
        Rob Landley <>,
        Bernd Edlinger <>,, Al Viro <>,
        Alexey Dobriyan <>,
        Andrew Morton <>
Subject: Re: [PATCH 6/6] exec: Set the point of no return sooner

On Fri, May 08, 2020 at 01:48:13PM -0500, Eric W. Biederman wrote:
> Make the code more robust by marking the point of no return sooner.
> This ensures that future code changes don't need to worry about how
> they return errors if they are past this point.
> This results in no actual change in behavior as __do_execve_file does
> not force SIGSEGV when there is a pending fatal signal pending past
> the point of no return.  Further the only error returns from de_thread
> and exec_mmap that can occur result in fatal signals being pending.
> Signed-off-by: "Eric W. Biederman" <>

Yes, thank you. I'm a fan; this makes the comment above the function a
bit easier to understand, since the very first thing is to set the
point_of_no_return. :)

Reviewed-by: Kees Cook <>

Kees Cook

Powered by blists - more mailing lists