linux-kernel - Re: [PATCH 1/2] fs/exec: allow to unshare a time namespace on vfork+exec

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] [day] [month] [year] [list]

Message-Id: <165530530544.261757.10728167525988459977.b4-ty@chromium.org>
Date:   Wed, 15 Jun 2022 08:01:48 -0700
From:   Kees Cook <keescook@...omium.org>
To:     avagin@...il.com, linux-kernel@...r.kernel.org,
        0x7f454c46@...il.com, brauner@...nel.org
Cc:     Kees Cook <keescook@...omium.org>, ebiederm@...ssion.com,
        linux-mm@...ck.org, fweimer@...hat.com
Subject: Re: [PATCH 1/2] fs/exec: allow to unshare a time namespace on vfork+exec

On Sun, 12 Jun 2022 23:07:22 -0700, Andrei Vagin wrote:
> Right now, a new process can't be forked in another time namespace
> if it shares mm with its parent. It is prohibited, because each time
> namespace has its own vvar page that is mapped into a process address
> space.
> 
> When a process calls exec, it gets a new mm and so it could be "legal"
> to switch time namespace in that case. This was not implemented and
> now if we want to do this, we need to add another clone flag to not
> break backward compatibility.
> 
> [...]

Applied to for-next/execve, thanks!

[1/2] fs/exec: allow to unshare a time namespace on vfork+exec
      https://git.kernel.org/kees/c/133e2d3e81de
[2/2] testing/timens: add a test for vfork+exit
      https://git.kernel.org/kees/c/6342140db660

-- 
Kees Cook