====================================================== WARNING: possible circular locking dependency detected 4.14.289-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/13606 is trying to acquire lock: (sb_writers#6){.+.+}, at: [] file_start_write include/linux/fs.h:2714 [inline] (sb_writers#6){.+.+}, at: [] vfs_fallocate+0x5c1/0x790 fs/open.c:318 but task is already holding lock: (ashmem_mutex){+.+.}, at: [] ashmem_shrink_scan drivers/staging/android/ashmem.c:494 [inline] (ashmem_mutex){+.+.}, at: [] ashmem_ioctl+0x27e/0xd00 drivers/staging/android/ashmem.c:843 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (ashmem_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 ashmem_mmap+0x50/0x5c0 drivers/staging/android/ashmem.c:393 call_mmap include/linux/fs.h:1785 [inline] mmap_region+0xa1a/0x1220 mm/mmap.c:1717 do_mmap+0x5b3/0xcb0 mm/mmap.c:1495 do_mmap_pgoff include/linux/mm.h:2187 [inline] vm_mmap_pgoff+0x14e/0x1a0 mm/util.c:366 SYSC_mmap_pgoff mm/mmap.c:1545 [inline] SyS_mmap_pgoff+0x249/0x510 mm/mmap.c:1503 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #2 (&mm->mmap_sem){++++}: __might_fault mm/memory.c:4705 [inline] __might_fault+0x137/0x1b0 mm/memory.c:4690 _copy_to_user+0x27/0xd0 lib/usercopy.c:25 copy_to_user include/linux/uaccess.h:155 [inline] filldir+0x1d5/0x390 fs/readdir.c:237 dir_emit_dot include/linux/fs.h:3361 [inline] dir_emit_dots include/linux/fs.h:3372 [inline] dcache_readdir+0x180/0x860 fs/libfs.c:192 iterate_dir+0x1a0/0x5e0 fs/readdir.c:52 SYSC_getdents fs/readdir.c:272 [inline] SyS_getdents+0x125/0x240 fs/readdir.c:253 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #1 (&type->i_mutex_dir_key#5){++++}: down_write+0x34/0x90 kernel/locking/rwsem.c:54 inode_lock include/linux/fs.h:719 [inline] do_last fs/namei.c:3331 [inline] path_openat+0xde2/0x2970 fs/namei.c:3569 do_filp_open+0x179/0x3c0 fs/namei.c:3603 do_sys_open+0x296/0x410 fs/open.c:1081 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (sb_writers#6){.+.+}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x64/0x260 fs/super.c:1342 file_start_write include/linux/fs.h:2714 [inline] vfs_fallocate+0x5c1/0x790 fs/open.c:318 ashmem_shrink_scan.part.0+0x135/0x3d0 drivers/staging/android/ashmem.c:501 ashmem_shrink_scan drivers/staging/android/ashmem.c:494 [inline] ashmem_ioctl+0x294/0xd00 drivers/staging/android/ashmem.c:843 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb other info that might help us debug this: Chain exists of: sb_writers#6 --> &mm->mmap_sem --> ashmem_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(ashmem_mutex); lock(&mm->mmap_sem); lock(ashmem_mutex); lock(sb_writers#6); *** DEADLOCK *** 1 lock held by syz-executor.2/13606: #0: (ashmem_mutex){+.+.}, at: [] ashmem_shrink_scan drivers/staging/android/ashmem.c:494 [inline] #0: (ashmem_mutex){+.+.}, at: [] ashmem_ioctl+0x27e/0xd00 drivers/staging/android/ashmem.c:843 stack backtrace: CPU: 0 PID: 13606 Comm: syz-executor.2 Not tainted 4.14.289-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x64/0x260 fs/super.c:1342 file_start_write include/linux/fs.h:2714 [inline] vfs_fallocate+0x5c1/0x790 fs/open.c:318 ashmem_shrink_scan.part.0+0x135/0x3d0 drivers/staging/android/ashmem.c:501 ashmem_shrink_scan drivers/staging/android/ashmem.c:494 [inline] ashmem_ioctl+0x294/0xd00 drivers/staging/android/ashmem.c:843 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x7f01e0400209 RSP: 002b:00007f01ded75168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f01e0512f60 RCX: 00007f01e0400209 RDX: 0000000000000000 RSI: 000000000000770a RDI: 0000000000000004 RBP: 00007f01e045a161 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffbebba7cf R14: 00007f01ded75300 R15: 0000000000022000 EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue [U] threaded EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue [U] threaded [U] threaded EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue [U] threaded EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue [U] threaded [U] threaded [U] threaded [U] threaded [U] threaded 9pnet: p9_errstr2errno: server reported unknown error ›Á“Ã;agj 9pnet: p9_errstr2errno: server reported unknown error ›Á“Ã;agj EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.4: iget: checksum invalid 9pnet: p9_errstr2errno: server reported unknown error ›Á“Ã;agj 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link 9pnet: p9_errstr2errno: server reported unknown error ›Á“Ã;agj bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode syz-executor.1 (13909) used greatest stack depth: 24112 bytes left EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.4: iget: checksum invalid device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state syz-executor.1 (13957) used greatest stack depth: 23952 bytes left bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.4: iget: checksum invalid device team_slave_1 entered promiscuous mode device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.5: iget: checksum invalid bridge0: port 3(team0) entered disabled state 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.3: iget: checksum invalid EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.2: iget: checksum invalid 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state 8021q: adding VLAN 0 to HW filter on device team0 EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.4: iget: checksum invalid bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode device team0 left promiscuous mode EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.5: iget: checksum invalid device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.2: iget: checksum invalid 8021q: adding VLAN 0 to HW filter on device team0 EXT4-fs error (device sda1): swap_inode_boot_loader:114: inode #5: comm syz-executor.1: iget: checksum invalid bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode syz-executor.0 (14077) used greatest stack depth: 23800 bytes left (syz-executor.4,14158,0):ocfs2_parse_options:1498 ERROR: Invalid heartbeat mount options (syz-executor.4,14158,0):ocfs2_fill_super:1217 ERROR: status = -22 (syz-executor.4,14184,0):ocfs2_parse_options:1498 ERROR: Invalid heartbeat mount options (syz-executor.4,14184,0):ocfs2_fill_super:1217 ERROR: status = -22 (syz-executor.4,14205,1):ocfs2_parse_options:1498 ERROR: Invalid heartbeat mount options (syz-executor.4,14205,1):ocfs2_fill_super:1217 ERROR: status = -22 (syz-executor.4,14246,1):ocfs2_parse_options:1498 ERROR: Invalid heartbeat mount options (syz-executor.4,14246,0):ocfs2_fill_super:1217 ERROR: status = -22 nla_parse: 1 callbacks suppressed netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.1'. ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. ISO 9660 Extensions: Microsoft Joliet Level 0 ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.1'. ISO 9660 Extensions: Microsoft Joliet Level 0 netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.4' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.4' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.2' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.4' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.2' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.4' sets config #0 usb usb5: usbfs: interface 0 claimed by hub while 'syz-executor.2' sets config #0