From: Christian Brauner <brauner@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Eric Biederman <ebiederm@xmission.com>,
linux-fsdevel@vger.kernel.org, Jann Horn <jannh@google.com>,
Andy Lutomirski <luto@kernel.org>,
David Laight <David.Laight@ACULAB.COM>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] exec: Add comments on check_unsafe_exec() fs counting
Date: Wed, 19 Oct 2022 13:35:18 +0200 [thread overview]
Message-ID: <20221019113518.tmbuflcinmcy5uk2@wittgenstein> (raw)
In-Reply-To: <20221018071537.never.662-kees@kernel.org>
On Tue, Oct 18, 2022 at 12:17:24AM -0700, Kees Cook wrote:
> Add some comments about what the fs counting is doing in
> check_unsafe_exec() and how it relates to the call graph.
> Specifically, we can't force an unshare of the fs because
> of at least Chrome:
> https://lore.kernel.org/lkml/86CE201B-5632-4BB7-BCF6-7CB2C2895409@chromium.org/
>
> Cc: Eric Biederman <ebiederm@xmission.com>
> Cc: linux-fsdevel@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
Acked-by: Christian Brauner (Microsoft) <brauner@kernel.org>
prev parent reply other threads:[~2022-10-19 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 7:17 [PATCH] exec: Add comments on check_unsafe_exec() fs counting Kees Cook
2022-10-19 11:35 ` Christian Brauner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221019113518.tmbuflcinmcy5uk2@wittgenstein \
--to=brauner@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox