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.
