⬢ DragonFlyBSD Kernel Audit
DF-3039 / run.log
← back to finding ↓ download raw
===== DF-3039: int bn truncation in msdosfs_mkdir (>=1TiB FAT32) =====
firstcluster=0x80000020 hugesec=0x80012020 (~73728 clusters) size=1.00 TiB sparse
FAT MOUNT-OK (1TiB sparse, firstcluster=0x80000020)
dd FAT area signature before mkdir:
00000000  f8 ff ff ff ff ff ff ff  ff ff ff ff              |............|
0000000c
mkdir: /mnt/d: Invalid argument
mkdir rc=1
dd after mkdir+sync:
00000000  f8 ff ff ff ff ff ff ff  ff ff ff ff              |............|
0000000c
image apparent size:
-rw-r--r--  1 root  wheel  1099549392896 Oct 26 03:21 /root/f40/fat3039.img
===== control: small FAT32, mkdir works =====
newfs_msdos: 16366 clusters too few clusters for FAT32, need 65525
mount_msdos: /dev/vn1: Invalid argument
small mkdir OK (control)
umount: unmount of /mnt failed: Invalid argument
dscheck(vn1): negative bio_offset -1099511611392
dscheck(vn1): negative bio_offset -1099511611392
vn1: MBR magic not found; assume a COMPATIBILITY_SLICE (s0)
=== cleanup stuck mount ===
umount: unmount of /mnt failed: Invalid argument
vnconfig: VNIOCDETACH: Device not configured
=== control: 256M FAT32 ===
newfs_msdos: 32734 clusters too few clusters for FAT32, need 65525
mount_msdos: /dev/vn1: Invalid argument
mkdir: /mnt/d: File exists
umount: unmount of /mnt failed: Invalid argument
dscheck(vn1): negative bio_offset -1099511611392
dscheck(vn1): negative bio_offset -1099511611392
dscheck(vn1): negative bio_offset -1099511611392
dscheck(vn1): negative bio_offset -1099511611392