possible deadlock in do_page_mkwrite

Status: upstream: reported C repro on 2023/04/29 03:26
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+dde175863b2f8fc68611@syzkaller.appspotmail.com
First crash: 1255d, last: 14d
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: failed (error log, bisect log)
  
▶ ▼ Bug presence (3)
Date Name Commit Repro Result
2024/12/12 linux-6.1.y (ToT) e4d90d63d385 C [report] possible deadlock in do_page_mkwrite
2023/06/18 upstream (ToT) 45a3e24f65e9 C [report] possible deadlock in do_page_mkwrite
2024/12/12 upstream (ToT) 231825b2e1ff C Didn't crash
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in do_page_mkwrite (2) dri 4 5 614d 674d 0/29 auto-obsoleted due to no activity on 2025/05/09 03:36
linux-6.6 possible deadlock in do_page_mkwrite 4 1 175d 175d 0/2 auto-obsoleted due to no activity on 2026/07/22 19:15
upstream possible deadlock in do_page_mkwrite fs 4 syz, C error done 114 979d 1393d 0/29 auto-obsoleted due to no activity on 2024/04/09 15:57
upstream possible deadlock in do_page_mkwrite (3) prio:high kernfs 4 9 195d 477d 0/29 auto-obsoleted due to no activity on 2026/07/02 20:26
linux-5.15 possible deadlock in do_page_mkwrite missing-backport origin:upstream 4 syz, C done 21 39d 1211d 0/3 upstream: reported C repro on 2023/06/12 00:09
▶ ▼ Fix bisection attempts (9)
Created Duration User Patch Repo Result
2024/12/26 13:46 8h59m fix candidate upstream OK (1) job log
2024/10/15 00:27 0m bisect fix linux-6.1.y error job log
2024/09/06 12:19 1h46m bisect fix linux-6.1.y OK (0) job log log
2024/08/02 06:00 1h59m bisect fix linux-6.1.y OK (0) job log log
2024/06/19 06:48 2h10m bisect fix linux-6.1.y OK (0) job log log
2024/04/17 11:43 2h26m bisect fix linux-6.1.y OK (0) job log log
2024/02/02 15:22 2h29m bisect fix linux-6.1.y OK (0) job log log
2023/12/30 06:57 1h30m bisect fix linux-6.1.y OK (0) job log log
2023/08/01 23:36 2h58m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4436 is trying to acquire lock:
ffff888077869090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff888073fa2558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x16b/0x5c0 mm/memory.c:3009

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_pagefaults#2){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1897 [inline]
       sb_start_pagefault include/linux/fs.h:2001 [inline]
       filemap_page_mkwrite+0x167/0x630 mm/filemap.c:3545
       do_page_mkwrite+0x16b/0x5c0 mm/memory.c:3009
       wp_page_shared+0x167/0x370 mm/memory.c:3358
       handle_pte_fault mm/memory.c:5047 [inline]
       __handle_mm_fault mm/memory.c:5171 [inline]
       handle_mm_fault+0x1b1b/0x3d40 mm/memory.c:5292
       do_user_addr_fault+0x58e/0xb20 arch/x86/mm/fault.c:1338
       handle_page_fault arch/x86/mm/fault.c:1429 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1482
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xc2/0x120 mm/memory.c:5850
       reiserfs_ioctl+0x13b/0x320 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:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&sbi->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5678
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0x10d/0x260 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x2e7/0xe80 fs/fs-writeback.c:2500
       generic_update_time fs/inode.c:1946 [inline]
       inode_update_time fs/inode.c:1959 [inline]
       __file_update_time+0x21d/0x240 fs/inode.c:2147
       file_update_time+0x2f3/0x370 fs/inode.c:2178
       filemap_page_mkwrite+0x271/0x630 mm/filemap.c:3546
       do_page_mkwrite+0x16b/0x5c0 mm/memory.c:3009
       wp_page_shared+0x167/0x370 mm/memory.c:3358
       handle_pte_fault mm/memory.c:5047 [inline]
       __handle_mm_fault mm/memory.c:5171 [inline]
       handle_mm_fault+0x1b1b/0x3d40 mm/memory.c:5292
       do_user_addr_fault+0x58e/0xb20 arch/x86/mm/fault.c:1338
       handle_page_fault arch/x86/mm/fault.c:1429 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1482
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608

other info that might help us debug this:

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

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz.0.17/4436:
 #0: ffff88807b35b5d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
 #0: ffff88807b35b5d8 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5320 [inline]
 #0: ffff88807b35b5d8 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x2e/0x2f0 mm/memory.c:5382
 #1: ffff888073fa2558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x16b/0x5c0 mm/memory.c:3009

stack backtrace:
CPU: 0 PID: 4436 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5678
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
 reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0x10d/0x260 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x2e7/0xe80 fs/fs-writeback.c:2500
 generic_update_time fs/inode.c:1946 [inline]
 inode_update_time fs/inode.c:1959 [inline]
 __file_update_time+0x21d/0x240 fs/inode.c:2147
 file_update_time+0x2f3/0x370 fs/inode.c:2178
 filemap_page_mkwrite+0x271/0x630 mm/filemap.c:3546
 do_page_mkwrite+0x16b/0x5c0 mm/memory.c:3009
 wp_page_shared+0x167/0x370 mm/memory.c:3358
 handle_pte_fault mm/memory.c:5047 [inline]
 __handle_mm_fault mm/memory.c:5171 [inline]
 handle_mm_fault+0x1b1b/0x3d40 mm/memory.c:5292
 do_user_addr_fault+0x58e/0xb20 arch/x86/mm/fault.c:1338
 handle_page_fault arch/x86/mm/fault.c:1429 [inline]
 exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1482
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f7ab716d02d
Code: 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 48 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 <c5> fe 7f 07 c5 fe 7f 4f 20 c5 fe 7f 54 17 e0 c5 fe 7f 5c 17 c0 e9
RSP: 002b:00007ffd1978ebc8 EFLAGS: 00010283
RAX: 00002000000001c0 RBX: 0000000000000004 RCX: 0000000000000007
RDX: 0000000000000055 RSI: 0000001b2d021239 RDI: 00002000000001c0
RBP: fffffffffffffffe R08: 0000001b2d420000 R09: 0000000000000001
R10: 0000000000000055 R11: 0000000000000001 R12: 0000000000000000
R13: 00007f7ab7425fac R14: 0000000000017d85 R15: 00007f7ab7425fa0
 </TASK>

Crashes (19):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/21 05:51 linux-6.1.y 1a8763b93150 853b104b .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 do_page_mkwrite
2026/01/14 03:42 linux-6.1.y bec0e10ee67e 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 do_page_mkwrite
2023/09/16 10:28 linux-6.1.y 09045dae0d90 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2023/06/18 13:50 linux-6.1.y ca87e77a2ef8 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2024/03/11 07:19 linux-6.1.y 61adba85cc40 6ee49f2e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2025/12/19 04:17 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2025/02/21 00:34 linux-6.1.y 0cbb5f65e52f 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2024/03/14 18:13 linux-6.1.y 61adba85cc40 8d8ee116 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2023/11/27 07:43 linux-6.1.y 69e434a1cb21 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
2026/06/09 02:09 linux-6.1.y 228da13e907e 656e94c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2026/04/14 05:30 linux-6.1.y 8e8fc038cad5 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2025/11/04 02:34 linux-6.1.y f6e38ae624cf 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2025/09/17 07:08 linux-6.1.y 3db754f56897 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2025/01/04 17:51 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 do_page_mkwrite
2024/05/15 14:09 linux-6.1.y 909ba1f1b414 94b087b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2023/11/30 06:00 linux-6.1.y 6ac30d748bb0 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2023/11/22 18:12 linux-6.1.y 69e434a1cb21 03e12510 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2023/10/19 22:54 linux-6.1.y 7d24402875c7 42e1d524 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in do_page_mkwrite
2023/04/29 03:26 linux-6.1.y ca1c9012c941 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in do_page_mkwrite
* Struck through repros no longer work on HEAD.