From: Moinak Bhattacharyya <[email protected]>
To: Amir Goldstein <[email protected]>
Cc: Bernd Schubert <[email protected]>,
Miklos Szeredi <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [PATCH] Fuse: Add backing file support for uring_cmd
Date: Sat, 22 Feb 2025 16:13:43 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOQ4uxieuFTN4Ni4HoBsEvTPW_odWSo78-5shJTh3T2A-vzP=g@mail.gmail.com>
> So fc->backing_files_map are not really fds registered for IO,
> they are essential references to backing inodes.
That's essentially what registered FD's are, they fget() the FD and
stash them in an internal data structure. It's not necessarily for I/O
per se, its more a mechanism to ensure fast Uring access to a given FD.
> Could you explain how fd registration into the ring would help here?
From my understanding of the previous problem with passthrough, we want
to make sure that one can't issue arbitrary write() calls to the open
FUSE FD to sneak in an arbitrary file passthrough (I admit, I don't
fully understand the concern). In any case, this is obviated by using
URING-only mechanisms, right?
next prev parent reply other threads:[~2025-02-22 22:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:19 [PATCH] Fuse: Add backing file support for uring_cmd Moinak Bhattacharyya
2025-02-21 15:24 ` Bernd Schubert
2025-02-21 15:36 ` Moinak Bhattacharyya
2025-02-21 16:14 ` Bernd Schubert
2025-02-21 16:17 ` Bernd Schubert
2025-02-21 16:35 ` Amir Goldstein
2025-02-21 17:24 ` Bernd Schubert
2025-02-22 22:33 ` Moinak Bhattacharyya
2025-02-21 16:24 ` Amir Goldstein
2025-02-21 17:13 ` Bernd Schubert
2025-02-21 17:25 ` Amir Goldstein
2025-02-21 17:44 ` Bernd Schubert
2025-02-21 18:13 ` Moinak Bhattacharyya
2025-02-21 18:14 ` Moinak Bhattacharyya
2025-02-21 18:21 ` Amir Goldstein
2025-02-22 22:13 ` Moinak Bhattacharyya [this message]
2025-02-21 18:23 ` Bernd Schubert
2025-02-21 18:31 ` Amir Goldstein
2025-02-24 12:08 ` Miklos Szeredi
2025-02-24 16:06 ` Moinak Bhattacharyya
2025-02-24 16:24 ` Miklos Szeredi
2025-02-24 12:27 ` Pavel Begunkov
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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