syzbot


possible deadlock in vm_mmap_pgoff

Status: upstream: reported C repro on 2023/03/19 23:00
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+958355bd694fe8943178@syzkaller.appspotmail.com
First crash: 575d, last: 28d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2024/10/15 upstream (ToT) eca631b8fe80 C [report] possible deadlock in vm_mmap_pgoff
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in vm_mmap_pgoff origin:upstream C 36 8d09h 575d 0/3 upstream: reported C repro on 2023/03/20 04:41
linux-4.19 possible deadlock in vm_mmap_pgoff (2) C error 2 687d 690d 0/1 upstream: reported C repro on 2022/11/25 13:47
linux-4.19 possible deadlock in vm_mmap_pgoff 4 1167d 1290d 0/1 auto-closed as invalid on 2021/12/02 20:13
upstream possible deadlock in vm_mmap_pgoff reiserfs C inconclusive inconclusive 225 260d 1267d 0/28 auto-obsoleted due to no activity on 2024/04/27 11:44
linux-4.14 possible deadlock in vm_mmap_pgoff reiserfs C 4 615d 682d 0/1 upstream: reported C repro on 2022/12/03 00:54
Last patch testing requests (9)
Created Duration User Patch Repo Result
2024/10/15 01:59 0m retest repro linux-5.15.y error
2024/10/15 01:59 0m retest repro linux-5.15.y error
2024/10/15 01:59 0m retest repro linux-5.15.y error
2024/10/15 01:59 0m retest repro linux-5.15.y error
2024/10/15 01:09 0m retest repro linux-5.15.y error
2024/10/15 01:09 0m retest repro linux-5.15.y error
2024/10/15 01:09 0m retest repro linux-5.15.y error
2024/10/15 01:09 0m retest repro linux-5.15.y error
2024/10/15 00:17 0m retest repro linux-5.15.y error

Sample crash report:
REISERFS (device loop0): Using r5 hash to sort names
REISERFS (device loop0): using 3.5.x disk format
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
5.15.117-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor260/4188 is trying to acquire lock:
ffff8881423d6090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff888077374028 (&mm->mmap_lock#2){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
ffff888077374028 (&mm->mmap_lock#2){++++}-{3:3}, at: vm_mmap_pgoff+0x175/0x2d0 mm/util.c:549

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock#2){++++}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       __might_fault+0xb4/0x110 mm/memory.c:5311
       reiserfs_ioctl+0x11d/0x340 fs/reiserfs/ioctl.c:96
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

-> #0 (&sbi->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0xee/0x240 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2442
       generic_update_time fs/inode.c:1775 [inline]
       inode_update_time fs/inode.c:1788 [inline]
       touch_atime+0x3fa/0x680 fs/inode.c:1860
       file_accessed include/linux/fs.h:2447 [inline]
       generic_file_mmap+0xbf/0x120 mm/filemap.c:3392
       call_mmap include/linux/fs.h:2108 [inline]
       mmap_region+0x10e7/0x1670 mm/mmap.c:1791
       do_mmap+0x78d/0xe00 mm/mmap.c:1575
       vm_mmap_pgoff+0x1ca/0x2d0 mm/util.c:551
       ksys_mmap_pgoff+0x559/0x780 mm/mmap.c:1624
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz-executor260/4188:
 #0: ffff888077374028 (&mm->mmap_lock#2){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff888077374028 (&mm->mmap_lock#2){++++}-{3:3}, at: vm_mmap_pgoff+0x175/0x2d0 mm/util.c:549
 #1: ffff88806d836460 (sb_writers#11){.+.+}-{0:0}, at: file_accessed include/linux/fs.h:2447 [inline]
 #1: ffff88806d836460 (sb_writers#11){.+.+}-{0:0}, at: generic_file_mmap+0xbf/0x120 mm/filemap.c:3392

stack backtrace:
CPU: 0 PID: 4188 Comm: syz-executor260 Not tainted 5.15.117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0xee/0x240 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2442
 generic_update_time fs/inode.c:1775 [inline]
 inode_update_time fs/inode.c:1788 [inline]
 touch_atime+0x3fa/0x680 fs/inode.c:1860
 file_accessed include/linux/fs.h:2447 [inline]
 generic_file_mmap+0xbf/0x120 mm/filemap.c:3392
 call_mmap include/linux/fs.h:2108 [inline]
 mmap_region+0x10e7/0x1670 mm/mmap.c:1791
 do_mmap+0x78d/0xe00 mm/mmap.c:1575
 vm_mmap_pgoff+0x1ca/0x2d0 mm/util.c:551
 ksys_mmap_pgoff+0x559/0x780 mm/mmap.c:1624
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1410c00509
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 16 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd0cf1e548 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1410c00509
RDX: 0000000000800001 RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 0000000000000000 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 00007ffd0cf1e578
R13: 00007ffd0cf1e5d0 R14: 00007ffd0cf1e590 R15: 0000000000000141
 </TASK>

Crashes (52):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/17 12:45 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2023/06/09 00:54 linux-5.15.y d7af3e5ba454 058b3a5a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/08/06 12:13 linux-5.15.y 7e89efd3ae1c e1bdb00a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/06/22 16:59 linux-5.15.y 4878aadf2d15 edc5149a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/12 10:31 linux-5.15.y 284087d4f7d5 9026e142 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/09 18:30 linux-5.15.y 284087d4f7d5 05079661 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/01 10:19 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/06/01 19:03 linux-5.15.y 0ab06468cbd1 babc4389 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/03/19 23:00 linux-5.15.y 8020ae3c051d 7939252e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/01/22 07:39 linux-5.15.y ddcaf4999061 9bd8dcda .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2023/06/24 03:03 linux-5.15.y f67653019430 79782afc .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/03/13 16:16 linux-5.15.y 574362648507 db5b7ff0 .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/18 17:36 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/08/16 08:57 linux-5.15.y 7e89efd3ae1c e4bacdaf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/08/04 13:36 linux-5.15.y 7e89efd3ae1c 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/07/28 19:37 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/06/13 14:16 linux-5.15.y c61bd26ae81a a9616ff5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/05/14 01:27 linux-5.15.y 284087d4f7d5 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/05/12 15:50 linux-5.15.y 284087d4f7d5 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/04/29 06:14 linux-5.15.y b925f60c6ee7 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/04/29 06:14 linux-5.15.y b925f60c6ee7 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/04/27 18:33 linux-5.15.y b925f60c6ee7 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/04/25 23:50 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/04/25 23:33 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2023/10/13 05:21 linux-5.15.y 02e21884dcf2 6388bc36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in vm_mmap_pgoff
2024/09/17 04:35 linux-5.15.y 3a5928702e71 c673ca06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/08/23 20:58 linux-5.15.y fa93fa65db6e d7d32352 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/08/10 10:57 linux-5.15.y 7e89efd3ae1c 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/08/08 08:51 linux-5.15.y 7e89efd3ae1c de12cf65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/07/31 10:56 linux-5.15.y 7e89efd3ae1c 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/07/30 02:46 linux-5.15.y 7e89efd3ae1c 5187fc86 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/07/14 08:38 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/07/12 23:11 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/07/12 23:11 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/06/14 22:03 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/06/14 22:03 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/28 18:27 linux-5.15.y c61bd26ae81a 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/05/02 19:18 linux-5.15.y 284087d4f7d5 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/23 04:09 linux-5.15.y c52b9710c83d 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/15 08:15 linux-5.15.y fa3df276cd36 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/15 07:40 linux-5.15.y fa3df276cd36 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/04/15 07:40 linux-5.15.y fa3df276cd36 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2024/01/23 08:25 linux-5.15.y ddcaf4999061 1c0ecc51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/10/10 05:05 linux-5.15.y 1edcec18cfb7 c9be5398 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/08/03 08:42 linux-5.15.y 09996673e313 39a91c18 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/07/27 13:01 linux-5.15.y 09996673e313 41fe1bae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/07/17 15:29 linux-5.15.y d54cfc420586 20f8b3c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/06/17 02:57 linux-5.15.y 471e639e59d1 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/31 08:15 linux-5.15.y 0ab06468cbd1 09898419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/10 07:46 linux-5.15.y 8a7f2a5c5aa1 1964022b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/05/03 05:08 linux-5.15.y 8a7f2a5c5aa1 48e0a81d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
2023/04/10 18:22 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vm_mmap_pgoff
* Struck through repros no longer work on HEAD.