Re: [PATCH v12 0/2] fuse: add kernel-enforced request timeout option

Joanne Koong
2025-02-25T17:35:48Z

On Mon, Feb 24, 2025 at 6:04 PM Sergey Senozhatsky
<senozhatsky@chromium.org> wrote:
>
> On (25/01/22 13:55), Joanne Koong wrote:
> > There are situations where fuse servers can become unresponsive or
> > stuck, for example if the server is in a deadlock. Currently, there's
> > no good way to detect if a server is stuck and needs to be killed
> > manually.
> >
> > This patchset adds a timeout option where if the server does not reply to a
> > request by the time the timeout elapses, the connection will be aborted.
> > This patchset also adds two dynamically configurable fuse sysctls
> > "default_request_timeout" and "max_request_timeout" for controlling/enforcing
> > timeout behavior system-wide.
> >
> > Existing systems running fuse servers will not be affected unless they
> > explicitly opt into the timeout.
>
> Sorry folks, has this series stuck? I'm not sure I'm seeing it
> in linux-next.

I'm not seeing it in linux-next either.

These patches were merged last month into Miklos' for-next tree as
9afd7336f3ac (miklos/for-next) fuse: add default_request_timeout and
max_request_timeout sysctls
ac5eab212a58 fuse: add kernel-enforced timeout option for requests

but I no longer see these commits in his tree anymore.

Miklos, why were these patches taken out?

Thanks,
Joanne