FAT-fs (loop4): bread failed, FSINFO block (sector = 62877) EXT4-fs (loop1): VFS: Can't find ext4 filesystem ====================================================== [ INFO: possible circular locking dependency detected ] 4.9.203-syzkaller #0 Not tainted ------------------------------------------------------- syz-executor.4/10215 is trying to acquire lock: (&mm->mmap_sem){++++++}, at: [<00000000d6137585>] __do_page_fault+0x7bd/0xa60 arch/x86/mm/fault.c:1337 but task is already holding lock: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000000970581a>] inode_lock include/linux/fs.h:771 [inline] (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000000970581a>] generic_file_write_iter+0x9a/0x630 mm/filemap.c:3090 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: lock_acquire+0x133/0x3d0 kernel/locking/lockdep.c:3759 down_write+0x41/0xa0 kernel/locking/rwsem.c:52 inode_lock include/linux/fs.h:771 [inline] shmem_fallocate+0x143/0xab0 mm/shmem.c:2683 ashmem_shrink_scan drivers/staging/android/ashmem.c:462 [inline] ashmem_shrink_scan+0x1c3/0x4c0 drivers/staging/android/ashmem.c:446 ashmem_ioctl+0x29b/0xdd0 drivers/staging/android/ashmem.c:804 vfs_ioctl fs/ioctl.c:43 [inline] file_ioctl fs/ioctl.c:493 [inline] do_vfs_ioctl+0xb87/0x11d0 fs/ioctl.c:677 SYSC_ioctl fs/ioctl.c:694 [inline] SyS_ioctl+0x8f/0xc0 fs/ioctl.c:685 do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 entry_SYSCALL_64_after_swapgs+0x5d/0xdb lock_acquire+0x133/0x3d0 kernel/locking/lockdep.c:3759 __mutex_lock_common kernel/locking/mutex.c:521 [inline] mutex_lock_nested+0xc7/0x920 kernel/locking/mutex.c:621 ashmem_mmap+0x53/0x470 drivers/staging/android/ashmem.c:378 mmap_region+0x7e7/0xfa0 mm/mmap.c:1726 do_mmap+0x539/0xbc0 mm/mmap.c:1505 do_mmap_pgoff include/linux/mm.h:2066 [inline] vm_mmap_pgoff+0x179/0x1c0 mm/util.c:329 SYSC_mmap_pgoff mm/mmap.c:1555 [inline] SyS_mmap_pgoff+0xfa/0x1b0 mm/mmap.c:1513 SYSC_mmap arch/x86/kernel/sys_x86_64.c:96 [inline] SyS_mmap+0x16/0x20 arch/x86/kernel/sys_x86_64.c:87 do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 entry_SYSCALL_64_after_swapgs+0x5d/0xdb check_prev_add kernel/locking/lockdep.c:1828 [inline] check_prevs_add kernel/locking/lockdep.c:1938 [inline] validate_chain kernel/locking/lockdep.c:2265 [inline] __lock_acquire+0x2d22/0x4390 kernel/locking/lockdep.c:3345 lock_acquire+0x133/0x3d0 kernel/locking/lockdep.c:3759 down_read+0x44/0xb0 kernel/locking/rwsem.c:22 __do_page_fault+0x7bd/0xa60 arch/x86/mm/fault.c:1337 do_page_fault+0x28/0x30 arch/x86/mm/fault.c:1464 page_fault+0x25/0x30 arch/x86/entry/entry_64.S:956 generic_perform_write+0x1b6/0x500 mm/filemap.c:2930 __generic_file_write_iter+0x340/0x530 mm/filemap.c:3065 generic_file_write_iter+0x38a/0x630 mm/filemap.c:3093 new_sync_write fs/read_write.c:498 [inline] __vfs_write+0x3c1/0x560 fs/read_write.c:511 vfs_write+0x185/0x520 fs/read_write.c:559 SYSC_pwrite64 fs/read_write.c:649 [inline] SyS_pwrite64+0x13f/0x170 fs/read_write.c:636 do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 entry_SYSCALL_64_after_swapgs+0x5d/0xdb other info that might help us debug this: Chain exists of: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#10); lock(ashmem_mutex); lock(&sb->s_type->i_mutex_key#10); lock(&mm->mmap_sem); *** DEADLOCK *** 2 locks held by syz-executor.4/10215: #0: (sb_writers#6){.+.+.+}, at: [<00000000d73ea14f>] file_start_write include/linux/fs.h:2645 [inline] #0: (sb_writers#6){.+.+.+}, at: [<00000000d73ea14f>] vfs_write+0x3e9/0x520 fs/read_write.c:558 #1: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000000970581a>] inode_lock include/linux/fs.h:771 [inline] #1: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000000970581a>] generic_file_write_iter+0x9a/0x630 mm/filemap.c:3090 stack backtrace: CPU: 0 PID: 10215 Comm: syz-executor.4 Not tainted 4.9.203-syzkaller #0 ffff8801a009f5e8 ffffffff81b55f6b ffffffff83caf240 ffffffff83cb81b0 ffffffff83cee510 ffffffff8424ff40 ffff8801d01d17c0 ffff8801a009f640 ffffffff81406eaa dffffc0000000000 ffffffff840709c0 ffff8801d01d20c0 Call Trace: [<00000000620ee98e>] __dump_stack lib/dump_stack.c:15 [inline] [<00000000620ee98e>] dump_stack+0xcb/0x130 lib/dump_stack.c:56 [<000000006cd41baf>] print_circular_bug.cold+0x2f6/0x454 kernel/locking/lockdep.c:1202 [<00000000e105efc3>] check_prev_add kernel/locking/lockdep.c:1828 [inline] [<00000000e105efc3>] check_prevs_add kernel/locking/lockdep.c:1938 [inline] [<00000000e105efc3>] validate_chain kernel/locking/lockdep.c:2265 [inline] [<00000000e105efc3>] __lock_acquire+0x2d22/0x4390 kernel/locking/lockdep.c:3345 [<00000000f93e7e26>] lock_acquire+0x133/0x3d0 kernel/locking/lockdep.c:3759 [<00000000099927f7>] down_read+0x44/0xb0 kernel/locking/rwsem.c:22 [<00000000d6137585>] __do_page_fault+0x7bd/0xa60 arch/x86/mm/fault.c:1337 [<00000000b189854b>] do_page_fault+0x28/0x30 arch/x86/mm/fault.c:1464 [<00000000c81c77d6>] page_fault+0x25/0x30 arch/x86/entry/entry_64.S:956 [<00000000cd04e4b5>] generic_perform_write+0x1b6/0x500 mm/filemap.c:2930 [<00000000debe22dc>] __generic_file_write_iter+0x340/0x530 mm/filemap.c:3065 [<0000000008035d65>] generic_file_write_iter+0x38a/0x630 mm/filemap.c:3093 [<00000000c4a442d5>] new_sync_write fs/read_write.c:498 [inline] [<00000000c4a442d5>] __vfs_write+0x3c1/0x560 fs/read_write.c:511 [<00000000dd2f24d4>] vfs_write+0x185/0x520 fs/read_write.c:559 [<000000002d711a86>] SYSC_pwrite64 fs/read_write.c:649 [inline] [<000000002d711a86>] SyS_pwrite64+0x13f/0x170 fs/read_write.c:636 [<000000008447badf>] do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 [<000000001915c203>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 27549) FAT-fs (loop4): codepage cp437 not found FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 26785) EXT4-fs (loop1): VFS: Can't find ext4 filesystem device lo left promiscuous mode FAT-fs (loop4): codepage cp437 not found device lo entered promiscuous mode EXT4-fs (loop1): VFS: Can't find ext4 filesystem device lo left promiscuous mode EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 20769) FAT-fs (loop4): codepage cp437 not found EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): bread failed, FSINFO block (sector = 65316) EXT4-fs (loop1): VFS: Can't find ext4 filesystem EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 8101) FAT-fs (loop4): codepage cp437 not found device lo entered promiscuous mode device lo left promiscuous mode EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 22825) FAT-fs (loop4): codepage cp437 not found EXT4-fs (loop1): VFS: Can't find ext4 filesystem device lo entered promiscuous mode EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1321) EXT4-fs (loop1): VFS: Can't find ext4 filesystem FAT-fs (loop4): codepage cp437 not found