On Thu, Mar 07, 2024 at 11:45:59AM +0100, Christian Brauner wrote: > Right now fallocate() is restartable. You could get EINTR and then > retry. Changing this to fatal_signal_pending() would mean that this > property is lost. The task will have to be wiped. People made much the same argument when I removed the nfs 'intr' mount option. It hasn't actually caused any issues that I've seen. > If this is only done for the sake of the OOM killer then we can probably > try and change it. But then we'd need to also reflect that on the > manpage. It's part of POSIX, I wouldn't remove the manpage. I think it's a QoI issue; we should only check for fatal signals.
