====================================================== [ INFO: possible circular locking dependency detected ] 4.9.205-syzkaller #0 Not tainted ------------------------------------------------------- syz-executor.5/31855 is trying to acquire lock: (&mm->mmap_sem){++++++}, at: [<00000000034877c5>] __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: [<000000002246b09e>] inode_lock include/linux/fs.h:771 [inline] (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000002246b09e>] 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: -> #2 (&sb->s_type->i_mutex_key#10){+.+.+.}: 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 -> #1 (ashmem_mutex){+.+.+.}: 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 -> #0 (&mm->mmap_sem){++++++}: 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: &mm->mmap_sem --> ashmem_mutex --> &sb->s_type->i_mutex_key#10 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.5/31855: #0: (sb_writers#6){.+.+.+}, at: [<00000000619056fb>] file_start_write include/linux/fs.h:2645 [inline] #0: (sb_writers#6){.+.+.+}, at: [<00000000619056fb>] vfs_write+0x3e9/0x520 fs/read_write.c:558 #1: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000002246b09e>] inode_lock include/linux/fs.h:771 [inline] #1: (&sb->s_type->i_mutex_key#10){+.+.+.}, at: [<000000002246b09e>] generic_file_write_iter+0x9a/0x630 mm/filemap.c:3090 stack backtrace: CPU: 1 PID: 31855 Comm: syz-executor.5 Not tainted 4.9.205-syzkaller #0 ffff8801a83275e8 ffffffff81b55e6b ffffffff83caeb80 ffffffff83cb81b0 ffffffff83cdda70 ffffffff8424ff40 ffff8801d1bedf00 ffff8801a8327640 ffffffff81406e9a dffffc0000000000 ffffffff8406b240 ffff8801d1bee800 Call Trace: [<00000000af0662b7>] __dump_stack lib/dump_stack.c:15 [inline] [<00000000af0662b7>] dump_stack+0xcb/0x130 lib/dump_stack.c:56 [<00000000b1ef1e03>] print_circular_bug.cold+0x2f6/0x454 kernel/locking/lockdep.c:1202 [<0000000098e0a45f>] check_prev_add kernel/locking/lockdep.c:1828 [inline] [<0000000098e0a45f>] check_prevs_add kernel/locking/lockdep.c:1938 [inline] [<0000000098e0a45f>] validate_chain kernel/locking/lockdep.c:2265 [inline] [<0000000098e0a45f>] __lock_acquire+0x2d22/0x4390 kernel/locking/lockdep.c:3345 [<00000000ecd5952f>] lock_acquire+0x133/0x3d0 kernel/locking/lockdep.c:3759 [<000000003c0ff82a>] down_read+0x44/0xb0 kernel/locking/rwsem.c:22 [<00000000034877c5>] __do_page_fault+0x7bd/0xa60 arch/x86/mm/fault.c:1337 [<000000001ed0bae8>] do_page_fault+0x28/0x30 arch/x86/mm/fault.c:1464 [<000000003545d32d>] page_fault+0x25/0x30 arch/x86/entry/entry_64.S:956 [<0000000096c3845f>] generic_perform_write+0x1b6/0x500 mm/filemap.c:2930 [<00000000cd0a0cfb>] __generic_file_write_iter+0x340/0x530 mm/filemap.c:3065 [<0000000026e129f8>] generic_file_write_iter+0x38a/0x630 mm/filemap.c:3093 [<000000001c895df4>] new_sync_write fs/read_write.c:498 [inline] [<000000001c895df4>] __vfs_write+0x3c1/0x560 fs/read_write.c:511 [<00000000e5141846>] vfs_write+0x185/0x520 fs/read_write.c:559 [<00000000dbd6edd4>] SYSC_pwrite64 fs/read_write.c:649 [inline] [<00000000dbd6edd4>] SyS_pwrite64+0x13f/0x170 fs/read_write.c:636 [<00000000a228b720>] do_syscall_64+0x1ad/0x5c0 arch/x86/entry/common.c:288 [<000000003b4c8e90>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb EXT4-fs (loop5): Unrecognized mount option "þÿ?" or missing value EXT4-fs (loop5): failed to parse options in superblock: þÿ? EXT4-fs (loop5): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs (loop5): mounted filesystem without journal. Opts: þÿ?; ,errors=continue EXT4-fs (loop5): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967294 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs (loop5): bad geometry: block count 3943230949295160 exceeds size of device (41984 blocks) EXT4-fs warning: 2 callbacks suppressed EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs (loop5): bad geometry: block count 580964351930795064 exceeds size of device (23897 blocks) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs (loop5): bad geometry: block count 580964351930795064 exceeds size of device (23897 blocks) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs (loop5): Unrecognized mount option "€Ð" or missing value EXT4-fs (loop5): failed to parse options in superblock: €Ð EXT4-fs (loop5): bad geometry: block count 580964351930795064 exceeds size of device (66048 blocks) EXT4-fs (loop5): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode table for group 0 overlaps superblock [EXT4 FS bs=2048, gc=1, bpg=16384, ipg=128, mo=e0026018, mo2=0002] System zones: 0-7 EXT4-fs (loop5): mounting with "discard" option, but the device does not support discard EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs warning (device sda1): verify_group_input:102: Cannot add at group 4294967292 (only 16 groups) EXT4-fs (loop5): Unrecognized mount option "þÿ?" or missing value EXT4-fs (loop5): failed to parse options in superblock: þÿ? EXT4-fs (loop5): ext4_check_descriptors: Block bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode bitmap for group 0 overlaps superblock EXT4-fs (loop5): ext4_check_descriptors: Inode table for group 0 overlaps superblock EXT4-fs (loop5): mounted filesystem without journal. Opts: þÿ?; ,errors=continue