From: Miklos Szeredi <miklos@szeredi.hu>
To: Chen Linxuan <chenlinxuan@uniontech.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] fs: fuse: add backing_files control file
Date: Fri, 9 May 2025 17:16:09 +0200 [thread overview]
Message-ID: <CAJfpegvqSsa7XyQyO9ugv0=tLhLDg8GSyd8HO8TG2e_nLxJVHg@mail.gmail.com> (raw)
In-Reply-To: <CAC1kPDMweHDtktTt=aSFamPNUWjt8nKw09U_2EqyDNu28H6WWg@mail.gmail.com>
On Fri, 9 May 2025 at 17:11, Chen Linxuan <chenlinxuan@uniontech.com> wrote:
>
> On Fri, May 9, 2025 at 10:59 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> > And that has limitations, since fdinfo lacks a hierarchy. E.g.
> > recursively retrieving "hidden files" info is impractical.
>
> What does "recursively" refer to in this context?
> I am not entirely sure what kind of situation it implies.
> Do you mean, for example, when a fixed file is a FUSE fd and it has a
> backing file?
Yeah. I don't see any practical relevance today, but allowing to
retrieve any attribute of these hidden files (fdinfo and hidden files
included) is a good thing that the flat nature of the current fdinfo
inteface makes difficult.
I'd argue that many current uses of fdinfo could be enabled with the
listxattr/getxattr inteface and would improve usablility (no need to
parse the fdinfo file to skip unneeded info).
Thanks,
Miklos
>
> Thanks,
> Chen Linxuan
next prev parent reply other threads:[~2025-05-09 15:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 6:33 [PATCH v3 0/3] fuse: Expose more information of fuse backing files to userspace Chen Linxuan via B4 Relay
2025-05-09 6:33 ` [PATCH v3 1/3] fs: fuse: add const qualifier to fuse_ctl_file_conn_get() Chen Linxuan via B4 Relay
2025-05-09 7:21 ` Amir Goldstein
2025-05-09 6:33 ` [PATCH v3 2/3] fs: fuse: add backing_files control file Chen Linxuan via B4 Relay
2025-05-09 7:20 ` Amir Goldstein
2025-05-09 7:40 ` Chen Linxuan
2025-05-09 7:39 ` Chen Linxuan
2025-05-09 9:14 ` Amir Goldstein
2025-05-09 14:00 ` Miklos Szeredi
2025-05-09 14:43 ` Chen Linxuan
2025-05-09 14:59 ` Miklos Szeredi
2025-05-09 15:10 ` Chen Linxuan
2025-05-09 15:16 ` Miklos Szeredi [this message]
2025-05-11 9:55 ` Chen Linxuan
2025-05-12 8:27 ` Miklos Szeredi
2025-05-12 9:17 ` Christian Brauner
2025-05-12 9:23 ` Amir Goldstein
2025-05-12 10:06 ` Miklos Szeredi
2025-05-13 7:39 ` Christian Brauner
2025-05-13 7:57 ` Miklos Szeredi
2025-05-13 14:49 ` Miklos Szeredi
2025-06-20 6:12 ` Chen Linxuan
2025-07-02 5:11 ` Miklos Szeredi
2025-05-09 15:19 ` Amir Goldstein
2025-05-09 15:41 ` Miklos Szeredi
2025-05-09 6:33 ` [PATCH v3 3/3] fs: fuse: add more information to fdinfo Chen Linxuan via B4 Relay
2025-05-09 6:40 ` Chen Linxuan
2025-05-09 7:13 ` Amir Goldstein
2025-05-09 16:05 ` Miklos Szeredi
2025-05-09 7:36 ` [PATCH v3 0/3] fuse: Expose more information of fuse backing files to userspace Amir Goldstein
2025-05-09 13:14 ` Miklos Szeredi
2025-05-13 18:52 ` Joanne Koong
2025-05-14 8:50 ` Miklos Szeredi
2025-05-14 23:03 ` Joanne Koong
2025-05-15 3:17 ` Chen Linxuan
2025-05-15 19:02 ` Joanne Koong
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='CAJfpegvqSsa7XyQyO9ugv0=tLhLDg8GSyd8HO8TG2e_nLxJVHg@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=chenlinxuan@uniontech.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;
as well as URLs for NNTP newsgroup(s).