News for hackers. Stuff that matters.
Re:Debugging a FUSE deadlock in the Linux kernel by loeg on Friday May 19, 2023 @05:42PM (#36007172)
Should processes not be able to wait after exit_signals? That seems like a plausible invariant.
Re:Debugging a FUSE deadlock in the Linux kernel by tych0 on Friday May 19, 2023 @05:51PM (#36007239)
I think they definitely should not. I've considered sending a patch that adds a WARN() or some syzkaller test for it or something, especially now that I've seen it in other filesystems.
Re:Debugging a FUSE deadlock in the Linux kernel by loeg on Friday May 19, 2023 @06:00PM (#36007304)
Makes sense to me.
Re:Debugging a FUSE deadlock in the Linux kernel by avianlyric on Friday May 19, 2023 @05:52PM (#36007253)
I think that’s the point. Currently doing that will potentially result in a deadlock.
Re:Debugging a FUSE deadlock in the Linux kernel by loeg on Friday May 19, 2023 @05:59PM (#36007294)
Well, only if the wait is for userspace or a remote resource, right? Regular disks are sometimes considered infallible (or at least, the IO will timeout eventually in the generic SCSI logic) and might be ok to wait on.

To generalize a bit, I think the problem is doing any sort of interruptible wait -- because we can no longer be interrupted. Uninterruptible waits aren't any different without signal delivery. I might be oversimplifying, though.