OGAWA Hirofumi e0544273b7 fat: don't allow to mount if the FAT length == 0 ... commit b1b65750b8 upstream. If FAT length == 0, the image doesn't have any data. And it can be the cause of overlapping the root dir and FAT entries. Also Windows treats it as invalid format. Reported-by: syzbot+6f1624f937d9d6911e2d@syzkaller.appspotmail.com Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Cc: Marco Elver <elver@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Link: http://lkml.kernel.org/r/87r1wz8mrd.fsf@mail.parknet.co.jp Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2020-06-17 16:40:36 +02:00
..
Kconfig	…
Makefile	…
cache.c	…
dir.c	fat: delete an unnecessary check before brelse()	2019-09-25 17:51:40 -07:00
fat.h	…
fatent.c	fat: work around race with userspace's read via blockdev while mounting	2019-09-24 15:54:06 -07:00
file.c	…
inode.c	fat: don't allow to mount if the FAT length == 0	2020-06-17 16:40:36 +02:00
misc.c	…
namei_msdos.c	…
namei_vfat.c	…
nfs.c	…