[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b59c5361-c800-4157-89e9-36fb3faaba50@bsbernd.com>
Date: Tue, 16 Dec 2025 19:49:49 +0100
From: Bernd Schubert <bernd@...ernd.com>
To: Askar Safin <safinaskar@...il.com>, Luis Henriques <luis@...lia.com>
Cc: amir73il@...il.com, bschubert@....com, djwong@...nel.org,
hbirthelmer@....com, kchen@....com, kernel-dev@...lia.com,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mharvey@...ptrading.com, miklos@...redi.hu
Subject: Re: [RFC PATCH v2 0/6] fuse: LOOKUP_HANDLE operation
On 12/16/25 01:33, Askar Safin wrote:
> On Mon, Dec 15, 2025 at 3:08 PM Luis Henriques <luis@...lia.com> wrote:
>> No, this won't fix that. This patchset is just an attempt to be a step
>> closer to be able to restart a FUSE server. But other things will be
>> needed (including changes in the user-space server).
>
> So, fix for fuse+suspend is planned?
I have an idea about this, but this is not a one-liner and might not
work either. The hard part is wait_event() in request_wait_answer().
Probably also needs libfuse support, because libraries might complain
when they eventually reply, but the request is not there anymore. We can
work on this during my x-mas holidays (feel free to ping from next week
on), but please avoid posting about this in unrelated threads.
Thanks,
Bernd
Powered by blists - more mailing lists