[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be2abea2-3834-4029-ba76-e8b338e83415@linux.alibaba.com>
Date: Mon, 29 Dec 2025 14:03:02 +0800
From: Jingbo Xu <jefflexu@...ux.alibaba.com>
To: Horst Birthelmer <hbirthelmer@...glemail.com>,
Miklos Szeredi <miklos@...redi.hu>, Bernd Schubert <bschubert@....com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Horst Birthelmer <hbirthelmer@....com>, syzbot@...kaller.appspotmail.com
Subject: Re: [PATCH RFC v2 0/2] fuse: compound commands
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
Powered by blists - more mailing lists