syzbot


possible deadlock in vm_mmap_pgoff

Status: upstream: reported C repro on 2021/04/27 15:18
Labels: reiserfs (incorrect?)
Reported-by: syzbot+f619f7c0a2a5f87694e6@syzkaller.appspotmail.com
First crash: 780d, last: 1d03h

Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: possible deadlock in vm_mmap_pgoff (log)
Repro: C syz .config

Fix bisection: the fix commit could be any of (bisect log):
  7d2a07b76933 Linux 5.14
  3cc40a443a04 Merge tag 'nios2_fixes_v6.0' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in vm_mmap_pgoff 0 (2) 2021/07/23 15:16
Re: [syzbot] possible deadlock in vm_mmap_pgoff 2 (2) 2021/05/03 15:55
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 7 8d12h 81d 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 193d 196d 0/1 upstream: reported C repro on 2022/11/25 13:47
linux-4.19 possible deadlock in vm_mmap_pgoff 4 674d 796d 0/1 auto-closed as invalid on 2021/12/02 20:13
linux-5.15 possible deadlock in vm_mmap_pgoff origin:upstream C 8 1d01h 82d 0/3 upstream: reported C repro on 2023/03/19 23:00
linux-4.14 possible deadlock in vm_mmap_pgoff reiserfs C 4 121d 189d 0/1 upstream: reported C repro on 2022/12/03 00:54
Last patch testing requests (2)
Created Duration User Patch Repo Result
2022/10/22 19:30 16m retest repro upstream report log
2022/10/22 19:30 17m retest repro upstream OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0 Not tainted
------------------------------------------------------
syz-executor241/6969 is trying to acquire lock:
ffff88803114c090 (&sbi->lock
){+.+.}-{3:3}, at: reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff888017344da8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:110 [inline]
ffff888017344da8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x158/0x3b0 mm/util.c:541

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault mm/memory.c:5732 [inline]
       __might_fault+0x115/0x190 mm/memory.c:5725
       reiserfs_ioctl+0x1d2/0x330 fs/reiserfs/ioctl.c:96
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&sbi->lock
){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3113 [inline]
       check_prevs_add kernel/locking/lockdep.c:3232 [inline]
       validate_chain kernel/locking/lockdep.c:3847 [inline]
       __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
       lock_acquire kernel/locking/lockdep.c:5705 [inline]
       lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0xd2/0x260 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2424
       generic_update_time fs/inode.c:1859 [inline]
       inode_update_time fs/inode.c:1872 [inline]
       touch_atime+0x687/0x740 fs/inode.c:1944
       file_accessed include/linux/fs.h:2198 [inline]
       generic_file_mmap+0x119/0x150 mm/filemap.c:3600
       call_mmap include/linux/fs.h:1873 [inline]
       mmap_region+0x694/0x28d0 mm/mmap.c:2652
       do_mmap+0x831/0xf60 mm/mmap.c:1394
       vm_mmap_pgoff+0x1a2/0x3b0 mm/util.c:543
       ksys_mmap_pgoff+0x41f/0x5a0 mm/mmap.c:1440
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

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-executor241/6969:
 #0: ffff888017344da8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:110 [inline]
 #0: ffff888017344da8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x158/0x3b0 mm/util.c:541
 #1: ffff88802def2460 (sb_writers#10){.+.+}-{0:0}, at: file_accessed include/linux/fs.h:2198 [inline]
 #1: ffff88802def2460 (sb_writers#10){.+.+}-{0:0}, at: generic_file_mmap+0x119/0x150 mm/filemap.c:3600

stack backtrace:
CPU: 2 PID: 6969 Comm: syz-executor241 Not tainted 6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2188
 check_prev_add kernel/locking/lockdep.c:3113 [inline]
 check_prevs_add kernel/locking/lockdep.c:3232 [inline]
 validate_chain kernel/locking/lockdep.c:3847 [inline]
 __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
 lock_acquire kernel/locking/lockdep.c:5705 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0xd2/0x260 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2424
 generic_update_time fs/inode.c:1859 [inline]
 inode_update_time fs/inode.c:1872 [inline]
 touch_atime+0x687/0x740 fs/inode.c:1944
 file_accessed include/linux/fs.h:2198 [inline]
 generic_file_mmap+0x119/0x150 mm/filemap.c:3600
 call_mmap include/linux/fs.h:1873 [inline]
 mmap_region+0x694/0x28d0 mm/mmap.c:2652
 do_mmap+0x831/0xf60 mm/mmap.c:1394
 vm_mmap_pgoff+0x1a2/0x3b0 mm/util.c:543
 ksys_mmap_pgoff+0x41f/0x5a0 mm/mmap.c:1440
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f31bb5b0a99
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 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:00007f31bb55c2e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 0000000000000020 RCX: 00007f31bb5b0a99
RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 00007f31bb6367a8 R08: 0000000000000006 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 00007f31bb6367a0
R13: 00007f31bb6031f8 R14: 7366726573696572 R15: 632e79726f6d656d
 </TASK>

Crashes (75):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/06/08 22:24 upstream 5f63595ebd82 058b3a5a .config console log report syz C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-qemu-upstream possible deadlock in vm_mmap_pgoff
2023/06/05 17:49 upstream 9561de3a55be a4ae4f42 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/06/01 07:05 upstream 48b1320a674e babc4389 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/20 03:03 upstream cbd6ac3837cd 96689200 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/13 12:32 upstream 9a48d6046722 2b9ba477 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/09 17:08 upstream ba0ad6ed89fd 30aa2a7e .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/31 22:07 upstream c8451c141e07 ab32d508 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/16 21:46 upstream 84e57d292203 05494336 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/10 18:00 upstream 3ecc37918c80 67be1ae7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2021/08/31 09:40 upstream 7d2a07b76933 8f58a0ef .config console log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in vm_mmap_pgoff
2023/04/01 00:22 linux-next 4b0f4525dc4f f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/02/05 23:49 linux-next 4fafd96910ad be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/06/01 10:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eb0f1697d729 babc4389 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in vm_mmap_pgoff
2023/05/20 05:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1fcbaa18b28 96689200 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in vm_mmap_pgoff
2023/01/21 03:10 upstream ff83fec8179e 559a440a .config strace log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2022/11/27 19:19 upstream faf68e3523c2 74a66371 .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2021/07/23 15:15 upstream 9bead1b58c4c bc5f1d88 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in vm_mmap_pgoff
2023/06/02 19:59 upstream 9e87b63ed37e a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/05/28 11:52 upstream 416839029e38 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/24 14:06 upstream 9d646009f65d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/24 00:32 upstream ae8373a5add4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/23 09:03 upstream 421ca22e3138 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/18 09:16 upstream 1b66c114d161 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/16 15:49 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/08 02:59 upstream 17784de648be 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/05/06 11:06 upstream 2e1e1337881b de870ca5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/30 23:27 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/30 07:10 upstream 1ae78a14516b 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/29 07:31 upstream 89d77f71f493 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/29 05:35 upstream 22b8cc3e78f5 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in vm_mmap_pgoff
2023/04/26 05:21 upstream 0cfd8703e7da 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/26 01:30 upstream 173ea743bf7a 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/25 00:44 upstream 1a0beef98b58 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/04/20 09:41 upstream cb0856346a60 a219f34e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/03/01 15:12 upstream c0927a7a5391 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/02/07 16:10 upstream 05ecb680708a 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/02/07 06:54 upstream 05ecb680708a 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/02/03 06:39 upstream e7368fd30165 33fc5c09 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/27 11:05 upstream 7c46948a6e9c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/22 14:58 upstream 2241ab53cbb5 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/21 01:43 upstream edc00350d205 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/19 21:21 upstream 081edded9b38 71197f3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/18 12:36 upstream c1649ec55708 4620c2d9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/17 16:39 upstream 6e50979a9c87 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/11 14:29 upstream 7dd4b804e080 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/11 02:01 upstream 40c18f363a08 48bc529a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/09 22:36 upstream 1fe4fd6f5cad 48bc529a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/07 15:37 upstream 0a71553536d2 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/07 15:23 upstream 0a71553536d2 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/05 05:48 upstream 512dee0c00ad 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/03 11:35 upstream 69b41ac87e4a f0036e18 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/03 11:04 upstream 69b41ac87e4a f0036e18 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2023/01/01 12:23 upstream e4cf7c25bae5 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/31 02:58 upstream bff687b3dad6 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/26 04:49 upstream 1b929c02afd3 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2022/12/18 12:01 upstream f9ff5644bcc0 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/18 08:43 upstream f9ff5644bcc0 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/10 08:02 upstream 3ecc37918c80 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/10 07:47 upstream 3ecc37918c80 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/09 01:13 upstream 479174d402bc 1034e5fa .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/04 11:51 upstream c2bf05db6c78 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in vm_mmap_pgoff
2022/12/01 10:20 upstream ef4d3ea40565 4c2a66e8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2021/10/17 04:18 upstream 304040fb4909 0c5d9412 .config console log report info ci-upstream-kasan-gce-root possible deadlock in vm_mmap_pgoff
2021/09/25 12:16 upstream 7d42e9818258 8cac236e .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in vm_mmap_pgoff
2021/09/25 08:31 upstream 4c4f0c2bf341 8cac236e .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in vm_mmap_pgoff
2021/09/24 22:43 upstream 4c4f0c2bf341 8cac236e .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in vm_mmap_pgoff
2021/09/24 21:29 upstream 4c4f0c2bf341 8cac236e .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in vm_mmap_pgoff
2021/04/20 10:31 upstream 7af08140979a c0ced557 .config console log report info ci-qemu-upstream possible deadlock in vm_mmap_pgoff
2023/04/26 22:44 linux-next b7455b10da76 19a3dabe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in vm_mmap_pgoff
2022/11/24 12:08 linux-next 15f3bff12cf6 12c66417 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in vm_mmap_pgoff
2023/05/30 10:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eb0f1697d729 8d5c7541 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in vm_mmap_pgoff
* Struck through repros no longer work on HEAD.