From: David Hildenbrand <david@redhat.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: linux-mm@kvack.org, kernel-dev@igalia.com, kernel@gpiccoli.net,
keescook@chromium.org, ebiederm@xmission.com, oleg@redhat.com,
yzaikin@google.com, mcgrof@kernel.org, akpm@linux-foundation.org,
brauner@kernel.org, viro@zeniv.linux.org.uk, willy@infradead.org,
dave@stgolabs.net, sonicadvance1@gmail.com, joshua@froggi.es
Subject: Re: [RFC PATCH 0/2] Introduce a way to expose the interpreted file with binfmt_misc
Date: Fri, 6 Oct 2023 14:07:16 +0200 [thread overview]
Message-ID: <e673d8d6-bfa8-be30-d1c1-fe09b5f811e3@redhat.com> (raw)
In-Reply-To: <20230907204256.3700336-1-gpiccoli@igalia.com>
On 07.09.23 22:24, Guilherme G. Piccoli wrote:
> Currently the kernel provides a symlink to the executable binary, in the
> form of procfs file exe_file (/proc/self/exe_file for example). But what
> happens in interpreted scenarios (like binfmt_misc) is that such link
> always points to the *interpreter*. For cases of Linux binary emulators,
> like FEX [0] for example, it's then necessary to somehow mask that and
> emulate the true binary path.
I'm absolutely no expert on that, but I'm wondering if, instead of
modifying exe_file and adding an interpreter file, you'd want to leave
exe_file alone and instead provide an easier way to obtain the
interpreted file.
Can you maybe describe why modifying exe_file is desired (about which
consumers are we worrying? ) and what exactly FEX does to handle that
(how does it mask that?).
So a bit more background on the challenges without this change would be
appreciated.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-10-06 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 20:24 Guilherme G. Piccoli
2023-09-07 20:24 ` [RFC PATCH 1/2] binfmt_misc, fork, proc: Introduce flag to expose the interpreted binary in procfs Guilherme G. Piccoli
2023-09-07 20:24 ` [RFC PATCH 2/2] fork, procfs: Introduce /proc/self/interpreter symlink Guilherme G. Piccoli
2023-10-06 7:51 ` [RFC PATCH 0/2] Introduce a way to expose the interpreted file with binfmt_misc Guilherme G. Piccoli
2023-10-06 12:07 ` David Hildenbrand [this message]
2023-10-09 17:37 ` Kees Cook
2023-10-11 23:53 ` Ryan Houdek
2023-11-13 17:33 ` Guilherme G. Piccoli
2023-11-13 18:29 ` Eric W. Biederman
2023-11-13 19:16 ` David Hildenbrand
2023-11-14 16:11 ` Eric W. Biederman
2023-11-14 16:14 ` David Hildenbrand
2023-11-13 19:17 ` Guilherme G. Piccoli
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=e673d8d6-bfa8-be30-d1c1-fe09b5f811e3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=gpiccoli@igalia.com \
--cc=joshua@froggi.es \
--cc=keescook@chromium.org \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=oleg@redhat.com \
--cc=sonicadvance1@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yzaikin@google.com \
/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