From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Horst Birthelmer <hbirthelmer@googlemail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Bernd Schubert <bschubert@ddn.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Horst Birthelmer <hbirthelmer@ddn.com>,
syzbot@syzkaller.appspotmail.com
Subject: Re: [PATCH RFC v2 0/2] fuse: compound commands
Date: Mon, 29 Dec 2025 14:03:02 +0800 [thread overview]
Message-ID: <be2abea2-3834-4029-ba76-e8b338e83415@linux.alibaba.com> (raw)
In-Reply-To: <20251223-fuse-compounds-upstream-v2-0-0f7b4451c85e@ddn.com>
Hi Horst & Bernd,
On 12/24/25 6:13 AM, Horst Birthelmer wrote:
> In the discussion about open+getattr here [1] Bernd and Miklos talked
> about the need for a compound command in fuse that could send multiple
> commands to a fuse server.
>
> Here's a propsal for exactly that compound command with an example
> (the mentioned open+getattr).
>
> [1] https://lore.kernel.org/linux-fsdevel/CAJfpegshcrjXJ0USZ8RRdBy=e0MxmBTJSCE0xnxG8LXgXy-xuQ@mail.gmail.com/
>
To achieve close-to-open, why not just invalidate the cached attr on
open so that the following access to the attr would trigger a new
FUSE_GETATTR request to fetch the latest attr from server?
--
Thanks,
Jingbo
next prev parent reply other threads:[~2025-12-29 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 22:13 Horst Birthelmer
2025-12-23 22:13 ` [PATCH RFC v2 1/2] fuse: add compound command to combine multiple requests Horst Birthelmer
2026-01-07 1:40 ` Joanne Koong
2026-01-07 9:29 ` Horst Birthelmer
2026-01-08 1:41 ` Joanne Koong
2026-01-07 14:03 ` Horst Birthelmer
2026-01-08 1:42 ` Joanne Koong
2025-12-23 22:13 ` [PATCH RFC v2 2/2] fuse: add an implementation of open+getattr Horst Birthelmer
2026-01-07 1:46 ` Joanne Koong
2026-01-07 9:03 ` Horst Birthelmer
2025-12-29 6:03 ` Jingbo Xu [this message]
2025-12-29 12:27 ` [PATCH RFC v2 0/2] fuse: compound commands Bernd Schubert
2025-12-30 8:36 ` Horst Birthelmer
2025-12-30 11:58 ` Jingbo Xu
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=be2abea2-3834-4029-ba76-e8b338e83415@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=bschubert@ddn.com \
--cc=hbirthelmer@ddn.com \
--cc=hbirthelmer@googlemail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=syzbot@syzkaller.appspotmail.com \
/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
all inboxes | Powered by JetHome®