Re: [PATCH 2/8] fuse: flush pending fuse events before aborting the connection

Miklos Szeredi
2025-09-30T10:29:43Z

On Wed, 24 Sept 2025 at 22:54, Darrick J. Wong <djwong@kernel.org> wrote:

> I think we don't want stuck task warnings because the "stuck" task
> (umount) is not the task that is actually doing the work.

Agreed.

I do wonder why this isn't happening during normal operation. There
could be multiple explanations:

- release is async, so this particular case would not trigger the hang warning

- some other op could be taking a long time to complete (fsync?), but
request_wait_answer() starts with interruptible sleep and falls back
to uninterruptible sleep after a signal is received. So unless
there's a signal, even a very slow request would fail to trigger the
hang warning.

A more generic solution would be to introduce a mechanism that would
tell the kernel that while the request is taking long, it's not
stalled (e.g. periodic progress reports).

But I also get the feeling that this is not very urgent and possibly
more of a test checkbox than a real life issue.

Thanks,
Miklos