syzbot


possible deadlock in ocfs2_page_mkwrite

Status: upstream: reported on 2024/09/16 20:58
Reported-by: syzbot+5dbd91eea2d01f1bc318@syzkaller.appspotmail.com
First crash: 367d, last: 10d
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ocfs2_page_mkwrite ocfs2 4 C done 1373 2d16h 371d 0/29 upstream: reported C repro on 2024/09/12 09:35
linux-6.1 possible deadlock in ocfs2_page_mkwrite 4 6 234d 318d 0/3 auto-obsoleted due to no activity on 2025/05/07 01:52
linux-6.1 possible deadlock in ocfs2_page_mkwrite (2) 4 10 4d09h 87d 0/3 upstream: reported on 2025/06/23 15:48
linux-6.6 possible deadlock in ocfs2_page_mkwrite 4 6 30d 70d 0/2 upstream: reported on 2025/07/10 06:01

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.115/4720 is trying to acquire lock:
ffff88805c4b0660 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_page_mkwrite+0x2ce/0xad0 fs/ocfs2/mmap.c:142

but task is already holding lock:
ffff888021d92558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922

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:1811 [inline]
       sb_start_pagefault include/linux/fs.h:1910 [inline]
       ocfs2_page_mkwrite+0x18a/0xad0 fs/ocfs2/mmap.c:122
       do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
       do_shared_fault mm/memory.c:4328 [inline]
       do_fault mm/memory.c:4396 [inline]
       handle_pte_fault mm/memory.c:4650 [inline]
       __handle_mm_fault mm/memory.c:4785 [inline]
       handle_mm_fault+0x1d4b/0x43c0 mm/memory.c:4883
       do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357
       handle_page_fault arch/x86/mm/fault.c:1445 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xb3/0x110 mm/memory.c:5357
       _copy_to_user+0x29/0x130 lib/usercopy.c:35
       copy_to_user include/linux/uaccess.h:200 [inline]
       fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144
       ocfs2_fiemap_inline fs/ocfs2/extent_map.c:725 [inline]
       ocfs2_fiemap+0x999/0xc40 fs/ocfs2/extent_map.c:762
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814
       __do_sys_ioctl fs/ioctl.c:872 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&oi->ip_alloc_sem){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       down_write+0x38/0x60 kernel/locking/rwsem.c:1551
       ocfs2_page_mkwrite+0x2ce/0xad0 fs/ocfs2/mmap.c:142
       do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
       do_shared_fault mm/memory.c:4328 [inline]
       do_fault mm/memory.c:4396 [inline]
       handle_pte_fault mm/memory.c:4650 [inline]
       __handle_mm_fault mm/memory.c:4785 [inline]
       handle_mm_fault+0x1d4b/0x43c0 mm/memory.c:4883
       do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357
       handle_page_fault arch/x86/mm/fault.c:1445 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606

other info that might help us debug this:

Chain exists of:
  &oi->ip_alloc_sem --> &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(&oi->ip_alloc_sem);

 *** DEADLOCK ***

2 locks held by syz.3.115/4720:
 #0: ffff888016868828 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock+0x1c/0x50 include/linux/mmap_lock.h:117
 #1: ffff888021d92558 (sb_pagefaults#2){.+.+}-{0:0}, at: do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922

stack backtrace:
CPU: 1 PID: 4720 Comm: syz.3.115 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 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 kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 down_write+0x38/0x60 kernel/locking/rwsem.c:1551
 ocfs2_page_mkwrite+0x2ce/0xad0 fs/ocfs2/mmap.c:142
 do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
 do_shared_fault mm/memory.c:4328 [inline]
 do_fault mm/memory.c:4396 [inline]
 handle_pte_fault mm/memory.c:4650 [inline]
 __handle_mm_fault mm/memory.c:4785 [inline]
 handle_mm_fault+0x1d4b/0x43c0 mm/memory.c:4883
 do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357
 handle_page_fault arch/x86/mm/fault.c:1445 [inline]
 exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606
RIP: 0033:0x7f39f237a1d9
Code: ff ff ff 01 64 48 8b 04 25 00 00 00 00 48 8d b8 c8 fe ff ff e8 68 59 0c 00 85 c0 75 10 48 8b 44 24 68 48 8b b4 24 98 00 00 00 <48> 89 30 64 f0 83 2c 25 90 ff ff ff 01 48 8b 84 24 80 00 00 00 48
RSP: 002b:00007ffe318f2dc0 EFLAGS: 00010246
RAX: 0000200000002680 RBX: 0000000000000002 RCX: fffffffffffffdbf
RDX: f7557da555eea3cb RSI: 0000200000000240 RDI: 000055559387a3c8
RBP: 00007f39f26dcda0 R08: 0000001b31520000 R09: 0000000000000009
R10: 0000000000000000 R11: 0000000000000001 R12: 00007f39f26dafac
R13: 00007f39f26dafa0 R14: fffffffffffffffe R15: 00007ffe318f2ed0
 </TASK>

Crashes (21):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/08 04:31 linux-5.15.y 7a6c2d093c45 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/08/17 21:55 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/08/17 21:53 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/08/17 21:51 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/06/19 20:06 linux-5.15.y 1c700860e8bc ed3e87f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/06/19 20:06 linux-5.15.y 1c700860e8bc ed3e87f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2024/09/27 23:02 linux-5.15.y 3a5928702e71 440b26ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2024/09/16 20:57 linux-5.15.y 3a5928702e71 c673ca06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_page_mkwrite
2025/08/15 07:23 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/08/15 07:21 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/07/25 22:35 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/05/31 02:38 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/05/25 18:18 linux-5.15.y 98f47d0e9b8c ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/05/05 01:49 linux-5.15.y 16fdf2c7111b b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/04/16 18:57 linux-5.15.y f7347f400572 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/04/15 14:37 linux-5.15.y f7347f400572 23b969b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/04/15 14:36 linux-5.15.y f7347f400572 23b969b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/04/03 22:49 linux-5.15.y 0c935c049b5c d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/01/08 06:36 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2025/01/08 06:36 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
2024/12/04 10:35 linux-5.15.y 0a51d2d4527b b50eb251 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_page_mkwrite
* Struck through repros no longer work on HEAD.