On Thu, 21 Aug 2025 at 02:51, Darrick J. Wong <djwong@xxxxxxxxxx> wrote: > Create a function to push all the background requests to the queue and > then wait for the number of pending events to hit zero, and call this > before fuse_abort_conn. That way, all the pending events are processed > by the fuse server and we don't end up with a corrupt filesystem. The flushing should be dependent on fc->destroy. Without that we really don't want server to block umount, not even for 30s. I hate timeout based solutions, so my preference would be to remove the timeout completely. It wouldn't really make a difference anyway, since FUSE_DESTROY is sent synchronously without a timeout. Thinking about blocking umount: if we did this in a private user/mount ns, then it wouldn't be a problem. But how can we be sure? Is checking sb->s_user_ns != &init_user_ns sufficient? Thanks, Miklos
