On Mon, Jan 03, 2022 at 07:49:11PM +0900, Tetsuo Handa wrote: > syzbot is reporting hung task at blkdev_fallocate() [1], for it can take > minutes with mapping->invalidate_lock held. Since fallocate() has to accept > size > MAX_RW_COUNT bytes, we can't predict how long it will take. Thus, > mitigate this problem by using killable wait where possible. Well, but that also means we want all other users of the invalidate_lock to be killable, as fallocate vs fallocate synchronization is probably not the interesting case. Or we should limit the locked batch size of block device fallocates that actually do write zeroes, which never really was the intent of the fallocate interface to start with..
