[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXEhTi2-8DRZKb_I@fedora>
Date: Wed, 21 Jan 2026 20:00:10 +0100
From: Horst Birthelmer <horst@...thelmer.de>
To: Bernd Schubert <bschubert@....com>
Cc: Bernd Schubert <bernd@...ernd.com>, Luis Henriques <luis@...lia.com>,
Amir Goldstein <amir73il@...il.com>, Miklos Szeredi <miklos@...redi.hu>,
"Darrick J. Wong" <djwong@...nel.org>, Kevin Chen <kchen@....com>,
Horst Birthelmer <hbirthelmer@....com>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Matt Harvey <mharvey@...ptrading.com>,
"kernel-dev@...lia.com" <kernel-dev@...lia.com>
Subject: Re: Re: [RFC PATCH v2 4/6] fuse: implementation of the
FUSE_LOOKUP_HANDLE operation
On Wed, Jan 21, 2026 at 07:49:25PM +0100, Bernd Schubert wrote:
>
>
...
> > The problem Luis had was that he cannot construct the second request in the compound correctly
> > since he does not have all the in parameters to write complete request.
>
> What I mean is, the auto-handler of libfuse could complete requests of
> the 2nd compound request with those of the 1st request?
>
With a crazy bunch of flags, we could probably do it, yes.
It is way easier that the fuse server treats certain compounds
(combination of operations) as a single request and handles
those accordingly.
> >> Thanks,
> >> Bernd
> >
> > Horst
>
Powered by blists - more mailing lists