From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 10/11] fhandle, pidfs: support open_by_handle_at() purely based on file handle
Date: Wed, 25 Jun 2025 00:07:45 +0100 [thread overview]
Message-ID: <20250624230745.GO1880847@ZenIV> (raw)
In-Reply-To: <20250624-work-pidfs-fhandle-v2-10-d02a04858fe3@kernel.org>
On Tue, Jun 24, 2025 at 10:29:13AM +0200, Christian Brauner wrote:
> Various filesystems such as pidfs (and likely drm in the future) have a
> use-case to support opening files purely based on the handle without
> having to require a file descriptor to another object. That's especially
> the case for filesystems that don't do any lookup whatsoever and there's
> zero relationship between the objects. Such filesystems are also
> singletons that stay around for the lifetime of the system meaning that
> they can be uniquely identified and accessed purely based on the file
> handle type. Enable that so that userspace doesn't have to allocate an
> object needlessly especially if they can't do that for whatever reason.
Whoa... Two notes:
1) you really want to make sure that no _directories_ on those
filesystems are decodable.
2) do you want to get the damn things bound somewhere?
next prev parent reply other threads:[~2025-06-24 23:07 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 8:29 [PATCH v2 00/11] fhandle, pidfs: allow open_by_handle_at() purely based on file handle Christian Brauner
2025-06-24 8:29 ` [PATCH v2 01/11] fhandle: raise FILEID_IS_DIR in handle_type Christian Brauner
2025-06-24 9:31 ` Jan Kara
2025-06-24 8:29 ` [PATCH v2 02/11] fhandle: hoist copy_from_user() above get_path_from_fd() Christian Brauner
2025-06-24 9:31 ` Jan Kara
2025-06-24 8:29 ` [PATCH v2 03/11] fhandle: rename to get_path_anchor() Christian Brauner
2025-06-24 9:31 ` Jan Kara
2025-06-24 8:29 ` [PATCH v2 04/11] pidfs: add pidfs_root_path() helper Christian Brauner
2025-06-24 9:31 ` Jan Kara
2025-06-24 8:29 ` [PATCH v2 05/11] fhandle: reflow get_path_anchor() Christian Brauner
2025-06-24 9:16 ` Jan Kara
2025-06-24 10:16 ` Christian Brauner
2025-06-24 8:29 ` [PATCH v2 06/11] uapi/fcntl: mark range as reserved Christian Brauner
2025-06-24 9:16 ` Jan Kara
2025-06-24 10:57 ` Amir Goldstein
2025-06-24 13:47 ` Christian Brauner
2025-06-24 8:29 ` [PATCH v2 07/11] uapi/fcntl: add FD_INVALID Christian Brauner
2025-06-24 9:17 ` Jan Kara
2025-06-24 8:29 ` [PATCH v2 08/11] exportfs: add FILEID_PIDFS Christian Brauner
2025-06-24 9:17 ` Jan Kara
2025-06-24 13:15 ` Amir Goldstein
2025-06-24 13:43 ` Christian Brauner
2025-06-24 14:20 ` Amir Goldstein
2025-06-24 8:29 ` [PATCH v2 09/11] fhandle: add EXPORT_OP_AUTONOMOUS_HANDLES marker Christian Brauner
2025-06-24 9:18 ` Jan Kara
2025-06-24 9:20 ` Jan Kara
2025-06-24 10:16 ` Christian Brauner
2025-06-24 8:29 ` [PATCH v2 10/11] fhandle, pidfs: support open_by_handle_at() purely based on file handle Christian Brauner
2025-06-24 9:30 ` Jan Kara
2025-06-24 10:15 ` Christian Brauner
2025-06-24 10:53 ` Amir Goldstein
2025-06-24 14:28 ` Amir Goldstein
2025-06-24 14:51 ` Christian Brauner
2025-06-24 15:07 ` Amir Goldstein
2025-06-24 15:23 ` Christian Brauner
2025-06-24 17:45 ` Jan Kara
2025-06-24 19:23 ` Amir Goldstein
2025-06-25 7:52 ` Christian Brauner
2025-06-24 23:07 ` Al Viro [this message]
2025-06-25 7:52 ` Christian Brauner
2025-06-24 8:29 ` [PATCH v2 11/11] selftests/pidfd: decode pidfd file handles withou having to specify an fd Christian Brauner
2025-06-24 9:39 ` Jan Kara
2025-06-24 10:58 ` [PATCH v2 00/11] fhandle, pidfs: allow open_by_handle_at() purely based on file handle Amir Goldstein
2025-06-24 10:59 ` Christian Brauner
2025-06-24 14:15 ` Jan Kara
2025-06-24 14:34 ` Amir Goldstein
2025-06-24 14:39 ` 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=20250624230745.GO1880847@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=simona@ffwll.ch \
/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