3 ms·

Are you sure this bug was not resolved long ago? My laptop auto-mounts a sshfs directory at startup and hibernates with no problem. On resume, the sshfs mount

Are you sure this bug was not resolved long ago? My laptop auto-mounts a sshfs directory at startup and hibernates with no problem. On resume, the sshfs mount still responds. Having an open shell on that directory is no problem, except that I can't manually unmount a FS being accessed. I remember configuring this when this Debian Testing laptop switched to systemd, years ago.

kasabali 6y ago
Not by a long shot. Simply being mounted isn't a problem. A syscall needs to be hung on a network request. I regularly hit this issue. Most recent one was last year on 4.19 kernel when using NFS mount. I found the bug report for that one and they said it was fixed in 5.1 or similar. Beware they were talking about that particular bug. Because as the parent comment says it is architectural issue that can't just be "fixed". It's a whack-a-mole. Developers need to be careful on all the call sites to avoid it. FUSE, NFS, CIFS code is all susceptible to it (and to my horror I've bitten by every single one of them several times in the past).