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

Miklos Szeredi
2025-09-24T18:20:12Z

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

> The wait_event_timeout() loop causes the process to schedule at least
> once per second, which avoids the "blocked for more than..." warning.
> Since the process actually does go to sleep, it's not necessary to touch
> the softlockup watchdog because we're not preventing another process
> from being scheduled on a CPU.

To be clear, this triggers because no RELEASE reply is received for
more than 20 seconds? That sounds weird. What is the server doing
all that time?

If a reply *is* received, then the task doing the umount should have
woken up (to check fc->num_waiting), which would have prevented the
hung task warning.

What am I missing?

Thanks,
Miklos