Thomas Frauendorfer 2bbd1e1e8a Fix off by one error in FAT16 <=> FAT32 detection ...

cluster_count is compared against FAT16_MAX, which is defined as 0xfff4
That is the maximum number of cluster a FAT16 can have.

For reference also check the  hardware whitepaper from Microsoft
FAT: General Overview of On-Disk Format, version 1.03 page 15

Signed-off-by: Thomas Frauendorfer <tf@miray.de>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

2019-03-15 09:57:24 +01:00

..

bcache.c

…

btrfs.c

…

Config.src

…

cramfs.c

…

exfat.c

…

ext.c

…

f2fs.c

…

fat.c

…

get_devname.c

…

hfs.c

…

iso9660.c

…

jfs.c

…

Kbuild.src

…

lfs.c

…

linux_raid.c

…

linux_swap.c

…

luks.c

…

minix.c

…

nilfs.c

…

ntfs.c

…

ocfs2.c

…

reiserfs.c

…

romfs.c

…

squashfs.c

…

sysv.c

…

ubifs.c

…

udf.c

…

unused_highpoint.c

…

unused_hpfs.c

…

unused_isw_raid.c

…

unused_lsi_raid.c

…

unused_lvm.c

…

unused_mac.c

…

unused_msdos.c

…

unused_nvidia_raid.c

…

unused_promise_raid.c

…

unused_silicon_raid.c

…

unused_ufs.c

…

unused_via_raid.c

…

util.c

…

volume_id_internal.h

…

volume_id.c

…

xfs.c

…