[mjevans]

It sounds like exit_signals() is being called too early, and based on the test case linked this might be a library issue rather than a code or kernel issue?

Edit: Reading the article it's more clear this happens in kernel's:

  do_exit() {
    ...
    exit_signals(tsk); /* sets PF_EXITING */
    ...
    exit_files(tsk);

Would a better solution not be to exit_signals(tsk); later in do_exit() after all possible signal sources are exhausted?

[cryptonector]

It doesn't matter. Filesystem waits are historically non-interruptible. The correct fix is indeed to allow the flushes to fail fast rather than wait forever.

[loeg]

> It sounds like exit_signals() is being called too early

Or zap_pid_ns too late, yeah.

[cryptonector]

Later would be better, no? Since it'd allow the FUSE process to outlive the init process, thus allowing the flushes to complete.