All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moinak Bhattacharyya <moinakb001@gmail.com>
To: Bernd Schubert <bernd@bsbernd.com>, Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	io-uring@vger.kernel.org
Subject: Re: [PATCH] Fuse: Add backing file support for uring_cmd
Date: Fri, 21 Feb 2025 12:13:04 -0600	[thread overview]
Message-ID: <72ac0bc2-ff75-4efe-987e-5002b7687729@gmail.com> (raw)
In-Reply-To: <2d9f56ae-7344-4f82-b5da-61522543ef4f@bsbernd.com>

I don't have the modifications to libfuse. What tree are you using for 
the uring modifications? I dont see any uring patches on the latest 
master liburing.
>> It is possible, for example set FOPEN_PASSTHROUGH_FD to
>> interpret backing_id as backing_fd, but note that in the current
>> implementation of passthrough_hp, not every open does
>> fuse_passthrough_open().
>> The non-first open of an inode uses a backing_id stashed in inode,
>> from the first open so we'd need different server logic depending on
>> the commands channel, which is not nice.
I wonder if we can just require URING registered FDs (using 
IORING_REGISTER_FILES). I think io_uring does checks on the file 
permissions when the FD is registered.

  reply	other threads:[~2025-02-21 18: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 [this message]
2025-02-21 18:14               ` Moinak Bhattacharyya
2025-02-21 18:21               ` Amir Goldstein
2025-02-22 22:13                 ` Moinak Bhattacharyya
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 \
    --in-reply-to=72ac0bc2-ff75-4efe-987e-5002b7687729@gmail.com \
    --to=moinakb001@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=bernd@bsbernd.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.