From: Christian Brauner <brauner@kernel.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: David Francis <David.Francis@amd.com>,
linux-kernel@vger.kernel.org, Alexander.Deucher@amd.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] fdinfo: Option for public fdinfo
Date: Tue, 24 Mar 2026 09:53:53 +0100 [thread overview]
Message-ID: <20260324-mitmachen-wirst-65daea421642@brauner> (raw)
In-Reply-To: <10ac8ef6-56b4-4a0f-b970-18b3ce012ceb@amd.com>
On Mon, Mar 23, 2026 at 02:16:59PM +0100, Christian König wrote:
> On 3/23/26 13:13, Christian Brauner wrote:
> > On Mon, Mar 16, 2026 at 02:38:28PM -0400, David Francis wrote:
> >> We want some GPU information to be publicly available to all
> >> processes for basic system-wide profiling (think GPU versions
> >> of top).
> >>
> >> This information is available in fdinfo and not easily exposed
> >> by other interfaces.
> >>
> >> Add fd_op flag FOP_PUBLIC_FDINFO, which, if set, makes the fdinfo
> >> for that file available to read for processes without ptrace
> >> permissions.
> >>
> >> Note that this makes public how many files each process has open,
> >> and what their fds are.
> >>
> >> Signed-off-by: David Francis <David.Francis@amd.com>
> >> ---
> >
> > Eew, please let's not. Add an ioctl if you need to be able to retrieve
> > that info.
>
> Yeah the problem is an IOCTL is even worse from the security pov.
>
> This is for an tool which doesn't have access to the file descriptor which provides that information.
>
> So using pidfd_getfd() or similar to get the FD and then call an IOCTL on it would be a security violation.
>
> The real question is how should we make this information public available in the system?
Don't you have a way to make this info available in sysfs? Just like
networking exposes info about network devices in there that may come and
go?
next prev parent reply other threads:[~2026-03-24 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 18:38 [RFC PATCH] fdinfo: Option for public fdinfo David Francis
2026-03-23 12:13 ` Christian Brauner
2026-03-23 13:16 ` Christian König
2026-03-24 8:53 ` Christian Brauner [this message]
2026-03-24 9:30 ` Christian König
2026-03-26 14:42 ` Christian Brauner
2026-03-30 18:49 ` Christian König
2026-04-07 10:30 ` Christian Brauner
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=20260324-mitmachen-wirst-65daea421642@brauner \
--to=brauner@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=David.Francis@amd.com \
--cc=christian.koenig@amd.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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