https://bugs.kde.org/show_bug.cgi?id=407313
--- Comment #3 from Tom Hughes <t...@compton.nu> --- The answer appears to be sys_newstat: SYSCALL[10855,1](4) sys_newstat ( 0x4ea48e0(/tmp/libfuse_test_LKz1UA), 0x1ffefff1a0 ) Which by the looks of it has not been marked as potentially blocking. I think we've been through this before - this use of fuse where the server is in the same process creates situations where system calls which would not normally be considered blocking are and I think we were reluctant to mark lots more system calls as blocking to support such as estoeric use case. -- You are receiving this mail because: You are watching all bug changes.
