[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202411021258.6F1CD2AE28@keescook>
Date: Sat, 2 Nov 2024 12:58:47 -0700
From: Kees Cook <kees@...nel.org>
To: Zbigniew Jędrzejewski-Szmek <zbyszek@...waw.pl>
Cc: Tycho Andersen <tycho@...ho.pizza>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Eric Biederman <ebiederm@...ssion.com>,
Shuah Khan <skhan@...uxfoundation.org>,
Aleksa Sarai <cyphar@...har.com>, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
Tycho Andersen <tandersen@...flix.com>
Subject: Re: [PATCH 1/2] exec: fix up /proc/pid/comm in the
execveat(AT_EMPTY_PATH) case
On Sat, Nov 02, 2024 at 11:29:55AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Oct 31, 2024 at 03:10:37PM -0700, Kees Cook wrote:
> > On Wed, 30 Oct 2024 14:37:31 -0600, Tycho Andersen wrote:
> > > Zbigniew mentioned at Linux Plumber's that systemd is interested in
> > > switching to execveat() for service execution, but can't, because the
> > > contents of /proc/pid/comm are the file descriptor which was used,
> > > instead of the path to the binary. This makes the output of tools like
> > > top and ps useless, especially in a world where most fds are opened
> > > CLOEXEC so the number is truly meaningless.
> > >
> > > [...]
> >
> > Applied to for-next/execve, thanks!
> >
> > [1/2] exec: fix up /proc/pid/comm in the execveat(AT_EMPTY_PATH) case
> > https://git.kernel.org/kees/c/7bdc6fc85c9a
> > [2/2] selftests/exec: add a test for execveat()'s comm
> > https://git.kernel.org/kees/c/bd104872311a
>
> I tested this with systemd compiled with -Dfexece=true and it all
> seems to work fine. Thanks!
Great; thank you!
--
Kees Cook
Powered by blists - more mailing lists