syzbot


possible deadlock in do_page_mkwrite

Status: auto-obsoleted due to no activity on 2024/04/09 15:57
Subsystems: reiserfs
[Documentation on labels]
Reported-by: syzbot+ff866d16791d4984b3c7@syzkaller.appspotmail.com
First crash: 526d, last: 110d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) :
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000

  fs: Block writes to mounted block devices

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in do_page_mkwrite 0 (3) 2024/03/09 00:24
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in do_page_mkwrite origin:upstream C 10 4d10h 386d 0/3 upstream: reported C repro on 2023/04/29 03:26
linux-5.15 possible deadlock in do_page_mkwrite origin:upstream C 6 3d03h 343d 0/3 upstream: reported C repro on 2023/06/12 00:09
Last patch testing requests (11)
Created Duration User Patch Repo Result
2024/02/13 20:23 23m retest repro linux-next OK log
2024/02/13 20:23 23m retest repro upstream OK log
2024/02/13 20:23 23m retest repro upstream OK log
2024/02/13 20:23 48m retest repro linux-next OK log
2024/01/30 06:39 23m retest repro upstream OK log
2024/01/30 06:39 22m retest repro upstream OK log
2024/01/30 06:39 26m retest repro upstream OK log
2024/01/30 06:39 35m retest repro upstream OK log
2024/01/30 06:39 54m retest repro upstream OK log
2024/01/29 04:13 18m retest repro upstream OK log
2022/12/23 11:27 28m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2024/03/08 19:23 4h59m bisect fix upstream job log (1)
2023/09/20 18:49 1h31m bisect fix upstream job log (0) log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.7.0-rc5-syzkaller-00230-g3b8a9b2e6809 #0 Not tainted
------------------------------------------------------
syz-executor156/5090 is trying to acquire lock:
ffff888019696090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff888029a94510 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:2944

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_pagefaults){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1635 [inline]
       sb_start_pagefault include/linux/fs.h:1739 [inline]
       filemap_page_mkwrite+0x174/0x7a0 mm/filemap.c:3577
       do_page_mkwrite+0x17a/0x380 mm/memory.c:2944
       do_shared_fault mm/memory.c:4705 [inline]
       do_fault mm/memory.c:4767 [inline]
       do_pte_missing mm/memory.c:3731 [inline]
       handle_pte_fault mm/memory.c:5039 [inline]
       __handle_mm_fault+0x2a3b/0x3d70 mm/memory.c:5180
       handle_mm_fault+0x47a/0xa10 mm/memory.c:5345
       do_user_addr_fault+0x3d1/0x1000 arch/x86/mm/fault.c:1413
       handle_page_fault arch/x86/mm/fault.c:1505 [inline]
       exc_page_fault+0x5d/0xc0 arch/x86/mm/fault.c:1561
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault mm/memory.c:5956 [inline]
       __might_fault+0x11f/0x1a0 mm/memory.c:5949
       reiserfs_ioctl+0x1c4/0x2e0 fs/reiserfs/ioctl.c:96
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl fs/ioctl.c:857 [inline]
       __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #0 (&sbi->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137
       lock_acquire kernel/locking/lockdep.c:5754 [inline]
       lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
       reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0xe6/0x270 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2452
       generic_update_time+0xcf/0xf0 fs/inode.c:1943
       inode_update_time fs/inode.c:1956 [inline]
       __file_update_time fs/inode.c:2144 [inline]
       file_update_time+0x12c/0x160 fs/inode.c:2174
       filemap_page_mkwrite+0x295/0x7a0 mm/filemap.c:3578
       do_page_mkwrite+0x17a/0x380 mm/memory.c:2944
       do_shared_fault mm/memory.c:4705 [inline]
       do_fault mm/memory.c:4767 [inline]
       do_pte_missing mm/memory.c:3731 [inline]
       handle_pte_fault mm/memory.c:5039 [inline]
       __handle_mm_fault+0x2a3b/0x3d70 mm/memory.c:5180
       handle_mm_fault+0x47a/0xa10 mm/memory.c:5345
       do_user_addr_fault+0x3d1/0x1000 arch/x86/mm/fault.c:1413
       handle_page_fault arch/x86/mm/fault.c:1505 [inline]
       exc_page_fault+0x5d/0xc0 arch/x86/mm/fault.c:1561
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

other info that might help us debug this:

Chain exists of:
  &sbi->lock --> &mm->mmap_lock --> sb_pagefaults

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz-executor156/5090:
 #0: ffff888018b7f6a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:165 [inline]
 #0: ffff888018b7f6a0 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5372 [inline]
 #0: ffff888018b7f6a0 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x35/0x580 mm/memory.c:5432
 #1: ffff888029a94510 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:2944

stack backtrace:
CPU: 1 PID: 5090 Comm: syz-executor156 Not tainted 6.7.0-rc5-syzkaller-00230-g3b8a9b2e6809 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 check_noncircular+0x317/0x400 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0xe6/0x270 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2452
 generic_update_time+0xcf/0xf0 fs/inode.c:1943
 inode_update_time fs/inode.c:1956 [inline]
 __file_update_time fs/inode.c:2144 [inline]
 file_update_time+0x12c/0x160 fs/inode.c:2174
 filemap_page_mkwrite+0x295/0x7a0 mm/filemap.c:3578
 do_page_mkwrite+0x17a/0x380 mm/memory.c:2944
 do_shared_fault mm/memory.c:4705 [inline]
 do_fault mm/memory.c:4767 [inline]
 do_pte_missing mm/memory.c:3731 [inline]
 handle_pte_fault mm/memory.c:5039 [inline]
 __handle_mm_fault+0x2a3b/0x3d70 mm/memory.c:5180
 handle_mm_fault+0x47a/0xa10 mm/memory.c:5345
 do_user_addr_fault+0x3d1/0x1000 arch/x86/mm/fault.c:1413
 handle_page_fault arch/x86/mm/fault.c:1505 [inline]
 exc_page_fault+0x5d/0xc0 arch/x86/mm/fault.c:1561
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f1aad278e00
Code: 09 00 00 00 e8 f1 43 03 00 48 8b 35 1a d3 0a 00 ba ff 7f 00 02 31 c0 bf 4d 00 00 00 e8 d9 43 03 00 31 c9 ba 42 da 14 00 31 c0 <c7> 04 25 c0 00 00 20 2e 2f 62 75 be c0 00 00 20 bf 02 00 00 00 66
RSP: 002b:00007ffe591027b0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 000000000014da42 RSI: 0000000002007fff RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000246 R12: 00007ffe591027dc
R13: 000000000000000e R14: 431bde82d7b634db R15: 00007ffe59102810
 </TASK>

Crashes (114):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/17 17:04 upstream 3b8a9b2e6809 3222d10c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root possible deadlock in do_page_mkwrite
2023/12/04 14:09 upstream 33cc938e65a9 f819d6f7 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/03 17:20 upstream 33cc938e65a9 f819d6f7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/16 04:05 upstream c42d9eeef8e5 cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/11/14 03:39 upstream b85ea95d0864 cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root possible deadlock in do_page_mkwrite
2023/11/01 15:04 upstream 89ed67ef126c 69904c9f .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/03 16:16 upstream ce36c8b14987 65faba36 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root possible deadlock in do_page_mkwrite
2023/06/20 10:29 upstream 692b7dc87ca6 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/06/13 16:17 upstream fb054096aea0 749afb64 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/05/15 20:29 upstream f1fcbaa18b28 c4d362e7 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/03/29 18:25 upstream fcd476ea6a88 f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/03/28 19:43 upstream 3a93e40326c8 48c74771 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/02/05 15:14 upstream 95078069c1e7 be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/01/17 10:19 upstream d532dd102151 a63719e7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/01/16 03:55 upstream 5dc4c995db9e a63719e7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2022/12/23 10:49 upstream 8395ae05cb5a 9da18ae8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/05/21 02:49 linux-next 715abedee4cd 4bce1a3e .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_page_mkwrite
2023/03/02 20:24 linux-next 26a4eaba02f7 f8902b57 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_page_mkwrite
2024/01/07 01:51 upstream 52b1853b080a d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2024/01/03 05:03 upstream 610a9b8f49fb fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/30 01:27 upstream f016f7547aee fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/29 12:01 upstream 8735c7c84d1b fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/28 15:58 upstream f5837722ffec fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/28 12:22 upstream f5837722ffec fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/28 01:21 upstream f5837722ffec fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/27 13:52 upstream fbafc3e621c3 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/27 11:52 upstream fbafc3e621c3 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/26 01:25 upstream fbafc3e621c3 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/22 06:52 upstream 9a6b294ab496 4f9530a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/21 21:17 upstream 9a6b294ab496 4f9530a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/20 15:44 upstream 55cb5f43689d de21eb89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/18 20:44 upstream 2cf4f94d8e86 924661f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/17 19:12 upstream 0e389834672c 3222d10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/17 03:30 upstream 3b8a9b2e6809 3222d10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/12 04:46 upstream 26aff849438c 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/12/11 06:56 upstream a39b6ac3781d 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/10 11:00 upstream c527f5606aa5 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/07 23:44 upstream 9ace34a8e446 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/06 07:20 upstream bee0e7762ad2 858d62d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/12/03 01:47 upstream 1b8af6552cb7 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/29 12:32 upstream 18d46e76d7c2 6e78f9ce .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/11/27 20:12 upstream 2cc14f52aeb7 7ec6c044 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/27 16:04 upstream 2cc14f52aeb7 7ec6c044 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/26 08:08 upstream 090472ed9c92 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/24 22:12 upstream f1a09972a45a 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/23 18:18 upstream 9b6de136b5f0 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/22 21:21 upstream 9b6de136b5f0 03e12510 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/22 00:33 upstream c2d5304e6c64 cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in do_page_mkwrite
2023/11/20 13:14 upstream 98b1cc82c4af cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/19 23:10 upstream eb3479bc23fa cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/18 19:18 upstream 23dfa043f6d5 cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/17 15:29 upstream 6bc40e44f1dd cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/16 14:45 upstream 7475e51b8796 cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/08 13:32 upstream 305230142ae0 83211397 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in do_page_mkwrite
2023/11/08 10:49 upstream 305230142ae0 83211397 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/05 12:51 upstream 1c41041124bd 500bfdc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/11/04 23:48 upstream aea6bf908d73 500bfdc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/31 11:49 upstream 5a6a09e97199 58499c95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/17 21:25 upstream 213f891525c2 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/16 19:29 upstream 58720809f527 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/15 21:20 upstream fbe1bf1e5ff1 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/15 07:32 upstream 9a3dad63edbe f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/10/14 04:50 upstream 8cb1f10d8c4b f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2023/05/25 09:34 upstream 933174ae28ba 54259e6c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in do_page_mkwrite
2022/12/11 03:07 upstream 296a7b7eb792 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2022/12/10 21:39 upstream 3ecc37918c80 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_page_mkwrite
2024/01/30 15:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 41bccc98fb79 7f400fcb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in do_page_mkwrite
2024/01/14 18:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in do_page_mkwrite
2023/10/29 21:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 3c418d72 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in do_page_mkwrite
2023/04/25 19:58 linux-next f600e0bbde85 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_page_mkwrite
* Struck through repros no longer work on HEAD.