fat: Relax checks for sector size and media type
Subsystems (2)
PATCH 1/1 fat: Relax checks for sector size and media type
Windows fastfat.sys driver accepts also media types 0x00 and 0x01 and sector sizes 128 and 256 bytes. Linux mkfs.fat can format disk also to larger FAT sector sizes then 4096 bytes, therefore relax also upper limit restriction.
---
Source code of Windows 10 Anniversary Update fastfat.sys driver is now available on github.
Check for valid media types in fastfat.sys is there:
https://github.com/Microsoft/Windows-driver-samples/blob/96eb96dfb613e4c745db6bd1f53a92fe7e2290fc/filesys/fastfat/fsctrl.c#L2601-L2611
And check for valid sector size is there:
https://github.com/Microsoft/Windows-driver-samples/blob/96eb96dfb613e4c745db6bd1f53a92fe7e2290fc/filesys/fastfat/fsctrl.c#L2542-L2547
--- fs/fat/inode.c | 4 +--- include/linux/msdos_fs.h | 2 +- 2 files changed, 2 insertions(+), 4 deletions(-)
fs/fat/inode.c +1 -3
@@ -1506,9 +1506,7 @@ static int fat_read_bpb(struct super_block *sb, struct fat_boot_sector *b, goto out; } -if (!is_power_of_2 (bpb->fat_sector_size) - || (bpb->fat_sector_size <512 ) - || (bpb->fat_sector_size >4096 )) { +if (!is_power_of_2 (bpb->fat_sector_size)) {if (!silent)fat_msg (sb,KERN_ERR ,"bogus logical sector size %u" , (unsigned )bpb->fat_sector_size);
include/linux/msdos_fs.h +1 -1
@@ -7,6 +7,6 @@/* media of boot sector */ static inline int fat_valid_media (u8 media) { -return 0xf8 <= media || media ==0xf0 ; +return 0xf8 <= media || media ==0xf0 || media ==0x00 || media ==0x01 ; }#endif /* !_LINUX_MSDOS_FS_H */
Signature · 1 line
2.11.0
OGAWA Hirofumi
maintainerfs/fat/inode.c static int fat_read_bpb(struct super_block *sb, struct fat_boot_sector *b, · line 1509
Quoted 9 lines · Pali Roh�r
Windows fastfat.sys driver accepts also media types
0x00and0x01and sector sizes 128 and 256 bytes. Linux mkfs.fat can format disk also to larger FAT sector sizes then 4096 bytes, therefore relax also upper limit restriction.fs/fat/inode.c +1
-3-if (!is_power_of_2 (bpb->fat_sector_size) - || (bpb->fat_sector_size <512 ) - || (bpb->fat_sector_size >4096 )) { +if (!is_power_of_2 (bpb->fat_sector_size)) {
Just relaxing validation doesn't work. The block layer doesn't support smaller than 512, and lager than PAGE_SIZE. (And in specification, fat doesn't support lager than 4096.)
include/linux/msdos_fs.h line 12
Quoted 6 lines
static inline int
fat_valid_media(u8 media)
{include/linux/msdos_fs.h +1
-1- return 0xf8 <= media || media == 0xf0; + return 0xf8 <= media || media == 0xf0 || media == 0x00 || media == 0x01; }#endif /* !_LINUX_MSDOS_FS_H */
This is ok though, this would be for ancient floppy media.
Thanks.
Signature · 1 line
OGAWA Hirofumi <[email protected]>
Quoted 7 lines · On Monday 03 September 2018 16:17:26 OGAWA Hirofumi wrote:
Quoted 4 lines · Pali Rohár
Windows fastfat.sys driver accepts also media types
0x00and0x01and sector sizes 128 and 256 bytes. Linux mkfs.fat can format disk also to larger FAT sector sizes then 4096 bytes, therefore relax also upper limit restriction.
Quoted 8 lines
fs/fat/inode.c static int fat_read_bpb(struct super_block *sb, struct fat_boot_sector *b, · line 1509
Quoted 4 lines
fs/fat/inode.c +1
-3-if (!is_power_of_2 (bpb->fat_sector_size) - || (bpb->fat_sector_size <512 ) - || (bpb->fat_sector_size >4096 )) { +if (!is_power_of_2 (bpb->fat_sector_size)) {Just relaxing validation doesn't work. The block layer doesn't support smaller than 512, and lager than
PAGE_SIZE. (And in specification, fat doesn't support lager than 4096.)
Hi! I just sent this patch for discussion, with links to (now open source) Windows implementation. I guess that Windows driver implementation is more "authoritative" then Microsoft's own specification. It is known that Windows implementation does not match Microsoft specification.
I know at least 3 FAT specifications (MS EFI FAT, MS/SD card FAT, ECMA-107) and you are right that Microsoft's one does not allow sector sizes larger then 4096.
If there is limitation by block layer, then:
1) Why we do not check for PAGE_SIZE?
2) Is check in fat driver really needed (if block layer checks it)?
Quoted 8 lines
include/linux/msdos_fs.h line 12
Quoted 6 lines
static inline int
fat_valid_media(u8 media)
{include/linux/msdos_fs.h +1
-1- return 0xf8 <= media || media == 0xf0; + return 0xf8 <= media || media == 0xf0 || media == 0x00 || media == 0x01; }#endif /* !_LINUX_MSDOS_FS_H */ This is ok though, this would be for ancient floppy media.
Ok.
Signature · 2 lines
Pali Rohár [email protected]
OGAWA Hirofumi
maintainerQuoted 10 lines · Pali Rohár
Quoted 3 lines
Just relaxing validation doesn't work. The block layer doesn't support smaller than 512, and lager than
PAGE_SIZE. (And in specification, fat doesn't support lager than 4096.)Hi! I just sent this patch for discussion, with links to (now open source) Windows implementation. I guess that Windows driver implementation is more "authoritative" then Microsoft's own specification. It is known that Windows implementation does not match Microsoft specification.
Quoted 7 lines
I know at least 3 FAT specifications (MS EFI FAT, MS/SD card FAT, ECMA-107) and you are right that Microsoft's one does not allow sector sizes larger then 4096.
If there is limitation by block layer, then:
1) Why we do not check for
PAGE_SIZE?
That source seems to check power_of_2(size) and 128 <= size <= 4096. Rather why do you want to support larger than 4096? Or I'm missing something?
Quoted 1 line
2) Is check in fat driver really needed (if block layer checks it)?
Yes, isolating block layer error and fat format error to be better error report.
Signature · 1 line
OGAWA Hirofumi <[email protected]>
Quoted 16 lines · On Monday 03 September 2018 17:01:03 OGAWA Hirofumi wrote:
Quoted 14 lines · Pali Rohár
Quoted 3 lines
Just relaxing validation doesn't work. The block layer doesn't support smaller than 512, and lager than
PAGE_SIZE. (And in specification, fat doesn't support lager than 4096.)Hi! I just sent this patch for discussion, with links to (now open source) Windows implementation. I guess that Windows driver implementation is more "authoritative" then Microsoft's own specification. It is known that Windows implementation does not match Microsoft specification.
I know at least 3 FAT specifications (MS EFI FAT, MS/SD card FAT, ECMA-107) and you are right that Microsoft's one does not allow sector sizes larger then 4096.
Quoted 7 lines
Quoted 3 lines
If there is limitation by block layer, then:
1) Why we do not check for
PAGE_SIZE?That source seems to check
power_of_2(size)and 128 <= size <= 4096. Rather why do you want to support larger than 4096? Or I'm missing something?
I looked into (Linux) mkfs.fat and it supports formatting disk also with sector size > 4096. Therefore I thought it may be good idea for ability to mount and use it (on Linux).
I could check what other operating system would do with FAT sector size larger then 4096.
Quoted 4 lines
Quoted 1 line
2) Is check in fat driver really needed (if block layer checks it)?
Yes, isolating block layer error and fat format error to be better error report.
Ok.
Signature · 2 lines
Pali Rohár [email protected]
OGAWA Hirofumi
maintainerQuoted 10 lines · Pali Rohár
Quoted 3 lines
That source seems to check
power_of_2(size)and 128 <= size <= 4096. Rather why do you want to support larger than 4096? Or I'm missing something?I looked into (Linux) mkfs.fat and it supports formatting disk also with sector size > 4096. Therefore I thought it may be good idea for ability to mount and use it (on Linux).
I could check what other operating system would do with FAT sector size larger then 4096.
If there is real user to use that, I'm ok though (of course, need serious tests). However, FAT would be for exchange data with other devices, and there is "cluster per sector", and spec recommends sector size == device sector size. So I suspect this format is not useful.
Thanks.
Signature · 1 line
OGAWA Hirofumi <[email protected]>
Quoted 10 lines · On Monday 03 September 2018 17:19:15 OGAWA Hirofumi wrote:
Quoted 8 lines · Pali Rohár
Quoted 3 lines
That source seems to check
power_of_2(size)and 128 <= size <= 4096. Rather why do you want to support larger than 4096? Or I'm missing something?I looked into (Linux) mkfs.fat and it supports formatting disk also with sector size > 4096. Therefore I thought it may be good idea for ability to mount and use it (on Linux).
Quoted 7 lines
Quoted 2 lines
I could check what other operating system would do with FAT sector size larger then 4096.
If there is real user to use that, I'm ok though (of course, need serious tests). However, FAT would be for exchange data with other devices, and there is "cluster per sector", and spec recommends sector size == device sector size. So I suspect this format is not useful.
I looked into OpenBSD, FreeBSD and NetBSD source code and there is no explicit upper limit for sector size. Just that sector size must be power of two.
I have not did tests yet, but you are right that some testing should be done.
As FAT operates with clusters and cluster size is defined by sector size, then sectors per cluster and sector size defines cluster size. And cluster size itself implies maximal size of FAT filesystem.
So increasing sector size could be useful to create larger FAT32 filesystems as current limit hit by sector size = 512 bytes.
What do you think, which operating systems should be tested?
Signature · 2 lines
Pali Rohár [email protected]
OGAWA Hirofumi
maintainerQuoted 12 lines · Pali Rohár
Quoted 4 lines
If there is real user to use that, I'm ok though (of course, need serious tests). However, FAT would be for exchange data with other devices, and there is "cluster per sector", and spec recommends sector size == device sector size. So I suspect this format is not useful.
I looked into OpenBSD, FreeBSD and NetBSD source code and there is no explicit upper limit for sector size. Just that sector size must be power of two.
I have not did tests yet, but you are right that some testing should be done.
Quoted 8 lines
As FAT operates with clusters and cluster size is defined by sector size, then sectors per cluster and sector size defines cluster size. And cluster size itself implies maximal size of FAT filesystem.
So increasing sector size could be useful to create larger FAT32 filesystems as current limit hit by sector size = 512 bytes.
What do you think, which operating systems should be tested?
Again, I suspect those custom extension (can't read by some uefi or windows) is not useful though.
Testing on kernel that has PAGE_SIZE >= 8192, and setting FAT sector_size >= 8192. After that, it would be safe to remove 4096 limitation.
Thanks.
Signature · 1 line
OGAWA Hirofumi <[email protected]>