On 2018/06/13 22:49, Tigran Aivazian wrote: > Having read the discussion carefully, I personally prefer to ignore > the fix as invalid, because mounting a filesystem image is a > privileged operation and if attempting to mount a corrupted image > causes a panic, that is no big deal, imho. While this report is triggered by a crafted filesystem image, I don't think that a legitimate but huge filesystem image crashes the system by hitting (size > KMALLOC_MAX_SIZE) path is nice. While filesystem should try to avoid such large allocation, there is no need to crash the system just because kmalloc() failed. e.g. http://lkml.kernel.org/r/927f24d4-b0c3-8192-5723-c314f38b4292@xxxxxxxxxxxxx
