0728695c63
Some combinations of FAT12 file system parameters could cause a kernel panic due to an unmapped access if the size of the FAT was larger than the CPU page size. The reason is that FAT12 uses 3 bytes to store 2 FAT pointers, leading to partial FAT pointers at the end of buffers of a size that is not a multiple of 3. With a typical page size of 4 KB, this caused the FAT entry at byte offsets 4095 and 4096 to cross the page boundary, with only the first page mapped. This was fixed by adjusting the mapping to always cover both bytes of each FAT entry. Testing revealed 2 other inconsistencies that are fixed by this commit: 1) The calculation of the size of the data area did not take into account the fact that the first two data block numbers are reserved and that the data area starts with block 2. This could cause a FAT12 file system created with the maximum supported number of blocks to be incorrectly identified as FAT16. 2) The root directory does not take up space in the data area of a FAT12 or FAT16 file system, since it is placed into a reserved area outside of that data area. This commits makes stat() report the logical size of the root directory, but with 0 blocks allocated from the data area. PR: 270587 Reviewed by: mckusick Differential Revision: https://reviews.freebsd.org/D39386 |
||
|---|---|---|
| .. | ||
| bootsect.h | ||
| bpb.h | ||
| denode.h | ||
| direntry.h | ||
| fat.h | ||
| msdosfs_conv.c | ||
| msdosfs_denode.c | ||
| msdosfs_fat.c | ||
| msdosfs_iconv.c | ||
| msdosfs_lookup.c | ||
| msdosfs_vfsops.c | ||
| msdosfs_vnops.c | ||
| msdosfsmount.h | ||