syzbot


possible deadlock in vm_mmap_pgoff

Status: upstream: reported C repro on 2023/03/20 04:41
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+e500ea0c0c680009b993@syzkaller.appspotmail.com
First crash: 1002d, last: 4d06h
Fix commit to backport (bisect log) :
tree: upstream
commit fb6f20ecb121cef4d7946f834a6ee867c4e21b4a
Author: Jan Kara <jack@suse.cz>
Date: Thu Oct 17 10:28:23 2024 +0000

  reiserfs: The last commit

  
Fix bisection: the issue occurs on the latest tested release (bisect log)
Crash: possible deadlock in vm_mmap_pgoff (log)
Repro: C syz .config
  
Bug presence (3)
Date Name Commit Repro Result
2024/12/09 linux-6.1.y (ToT) e4d90d63d385 C [report] possible deadlock in vm_mmap_pgoff
2023/05/11 upstream (ToT) 80e62bc8487b C [report] possible deadlock in vm_mmap_pgoff
2024/12/09 upstream (ToT) fac04efc5c79 C Didn't crash
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in vm_mmap_pgoff (2) 4 C error 2 1113d 1117d 0/1 upstream: reported C repro on 2022/11/25 13:47
linux-4.19 possible deadlock in vm_mmap_pgoff 4 4 1594d 1716d 0/1 auto-closed as invalid on 2021/12/02 20:13
linux-5.15 possible deadlock in vm_mmap_pgoff missing-backport origin:upstream 4 C done 68 7d02h 1002d 0/3 upstream: reported C repro on 2023/03/19 23:00
upstream possible deadlock in vm_mmap_pgoff fs 4 C inconclusive inconclusive 225 687d 1694d 0/29 auto-obsoleted due to no activity on 2024/04/27 11:44
linux-6.6 possible deadlock in vm_mmap_pgoff 4 1 51d 51d 0/2 upstream: reported on 2025/10/25 20:23
linux-4.14 possible deadlock in vm_mmap_pgoff reiserfs 4 C 4 1042d 1109d 0/1 upstream: reported C repro on 2022/12/03 00:54
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2024/12/24 11:10 9h17m fix candidate upstream OK (1) job log
2024/11/10 01:06 2h13m bisect fix linux-6.1.y OK (0) job log log
2024/10/07 06:54 3h20m bisect fix linux-6.1.y OK (0) job log log
2024/08/24 21:24 2h20m bisect fix linux-6.1.y OK (0) job log log
2024/06/09 20:54 2h26m bisect fix linux-6.1.y OK (0) job log log
2024/03/05 11:16 2h35m bisect fix linux-6.1.y OK (0) job log log
2023/04/19 04:41 1h00m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.52/4563 is trying to acquire lock:
ffff88805edd0090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff88802ed35b58 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
ffff88802ed35b58 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:518

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xc2/0x120 mm/memory.c:5852
       reiserfs_ioctl+0x13b/0x330 fs/reiserfs/ioctl.c:96
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&sbi->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
       lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
       reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0xf0/0x240 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x2eb/0xe90 fs/fs-writeback.c:2443
       generic_update_time fs/inode.c:1946 [inline]
       inode_update_time fs/inode.c:1959 [inline]
       touch_atime+0x3a7/0x620 fs/inode.c:2031
       file_accessed include/linux/fs.h:2600 [inline]
       generic_file_mmap+0xbe/0x120 mm/filemap.c:3579
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_file+0x5d/0xb0 mm/util.c:1109
       __mmap_region mm/mmap.c:2772 [inline]
       mmap_region+0xe2c/0x1c70 mm/mmap.c:2916
       do_mmap+0x958/0xfd0 mm/mmap.c:1436
       vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:520
       ksys_mmap_pgoff+0x516/0x6f0 mm/mmap.c:1482
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&mm->mmap_lock);
                               lock(&sbi->lock);
                               lock(&mm->mmap_lock);
  lock(&sbi->lock);

 *** DEADLOCK ***

2 locks held by syz.0.52/4563:
 #0: ffff88802ed35b58 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff88802ed35b58 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:518
 #1: ffff888076f7e460 (sb_writers#13){.+.+}-{0:0}, at: file_accessed include/linux/fs.h:2600 [inline]
 #1: ffff888076f7e460 (sb_writers#13){.+.+}-{0:0}, at: generic_file_mmap+0xbe/0x120 mm/filemap.c:3579

stack backtrace:
CPU: 1 PID: 4563 Comm: syz.0.52 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
 reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0xf0/0x240 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x2eb/0xe90 fs/fs-writeback.c:2443
 generic_update_time fs/inode.c:1946 [inline]
 inode_update_time fs/inode.c:1959 [inline]
 touch_atime+0x3a7/0x620 fs/inode.c:2031
 file_accessed include/linux/fs.h:2600 [inline]
 generic_file_mmap+0xbe/0x120 mm/filemap.c:3579
 call_mmap include/linux/fs.h:2270 [inline]
 mmap_file+0x5d/0xb0 mm/util.c:1109
 __mmap_region mm/mmap.c:2772 [inline]
 mmap_region+0xe2c/0x1c70 mm/mmap.c:2916
 do_mmap+0x958/0xfd0 mm/mmap.c:1436
 vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:520
 ksys_mmap_pgoff+0x516/0x6f0 mm/mmap.c:1482
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2a6158f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2a62462038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f2a617e6090 RCX: 00007f2a6158f749
RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000200000000000
RBP: 00007f2a61613f91 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2a617e6128 R14: 00007f2a617e6090 R15: 00007ffdaf9ebc88
 </TASK>

Crashes (51):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/12 09:41 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2025/12/05 19:56 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2024/01/27 09:49 linux-6.1.y 883d1a956208 cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/05/08 16:07 linux-6.1.y ca48fc16c493 90c93c40 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2024/04/09 12:13 linux-6.1.y 347385861c50 f3234354 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/03/17 18:35 linux-6.1.y d7543167affd d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/03/13 12:12 linux-6.1.y 61adba85cc40 db5b7ff0 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/12/11 05:01 linux-6.1.y 6c6a6c7e211c 28b24332 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/08/14 16:57 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/06/23 00:02 linux-6.1.y e84a4e368abe 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/06/11 19:27 linux-6.1.y 2f3918bc53fb 49519f06 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/08/21 08:20 linux-6.1.y 6c44e13dc284 d216d8a0 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/08/16 04:24 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/20 08:19 linux-6.1.y fa74641fb6b9 96689200 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/14 06:34 linux-6.1.y bf4ad6fa4e53 2b9ba477 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/03/15 19:16 linux-6.1.y 61adba85cc40 d615901c .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/07/08 23:48 linux-6.1.y 61fd484b2cf6 668cb1fa .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/06/01 13:17 linux-6.1.y d2869ace6eeb babc4389 .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/03/20 04:41 linux-6.1.y 7eaef76fbc46 7939252e .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/07/08 01:30 linux-6.1.y 04d1ccaa9c28 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2025/03/06 01:52 linux-6.1.y 3a8358583626 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2025/01/16 17:05 linux-6.1.y c63962be84ef f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2024/07/16 19:23 linux-6.1.y cac15753b8ce b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/12/22 23:19 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2023/10/11 03:41 linux-6.1.y 082280fe94a0 83165b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in vm_mmap_pgoff
2025/06/04 00:56 linux-6.1.y da3c5173c55f a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/05/28 09:31 linux-6.1.y da3c5173c55f 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/03/09 17:43 linux-6.1.y 6ae7ac5c4251 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/03/01 08:20 linux-6.1.y 3a8358583626 67cf5345 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/01/13 09:54 linux-6.1.y c63962be84ef 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2025/01/07 04:23 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/12/24 14:38 linux-6.1.y 29f02ec58a94 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/12/09 12:55 linux-6.1.y e4d90d63d385 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/10 03:53 linux-6.1.y 909ba1f1b414 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/06 09:05 linux-6.1.y 909ba1f1b414 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/05 21:45 linux-6.1.y 909ba1f1b414 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/30 13:51 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/22 02:47 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/03/14 17:54 linux-6.1.y 61adba85cc40 8d8ee116 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/01/25 20:55 linux-6.1.y 8fd7f4462453 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/01/01 15:47 linux-6.1.y a507f147e6f0 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/12/26 05:26 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/12/21 11:16 linux-6.1.y 4aa6747d9352 4f9530a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/11/28 23:22 linux-6.1.y 6ac30d748bb0 1adfb6f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/11/09 04:10 linux-6.1.y fb2635ac69ab 4862372a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/10/09 00:55 linux-6.1.y ecda77b46871 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/07/25 12:10 linux-6.1.y 5302e81aa209 3b91ad04 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/13 13:18 linux-6.1.y bf4ad6fa4e53 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/04/26 12:19 linux-6.1.y f17b0ab65d17 8d843721 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in vm_mmap_pgoff
* Struck through repros no longer work on HEAD.