* [syzbot] [mm?] [fs?] possible deadlock in page_cache_ra_order
@ 2026-05-31 2:05 syzbot
2026-09-14 19:17 ` [syzbot] [ntfs3?] " syzbot
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2026-05-31 2:05 UTC (permalink / raw)
To: akpm, jack, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs, willy
Hello,
syzbot found the following issue on:
HEAD commit: e7e28506af98 Add linux-next specific files for 20260526
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1377f67e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1701da6552dd9b8
dashboard link: https://syzkaller.appspot.com/bug?extid=8bd419f88e25ab12cb75
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0060088615f7/disk-e7e28506.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bee8a0723af7/vmlinux-e7e28506.xz
kernel image: https://storage.googleapis.com/syzbot-assets/040209574106/bzImage-e7e28506.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8bd419f88e25ab12cb75@syzkaller.appspotmail.com
loop4: detected capacity change from 0 to 4096
ntfs3(loop4): failed to convert "0080" to koi8-ru
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.188/6496 is trying to acquire lock:
ffff888062d66830 (mapping.invalidate_lock#3){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
ffff888062d66830 (mapping.invalidate_lock#3){++++}-{4:4}, at: do_page_cache_ra mm/readahead.c:349 [inline]
ffff888062d66830 (mapping.invalidate_lock#3){++++}-{4:4}, at: page_cache_ra_order+0x2b4/0x4a0 mm/readahead.c:562
but task is already holding lock:
ffff88803fd78888 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1214 [inline]
ffff88803fd78888 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_readdir+0x6c9/0xf40 fs/ntfs3/dir.c:497
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&ni->ni_lock/5){+.+.}-{4:4}:
__mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
ni_lock fs/ntfs3/ntfs_fs.h:1214 [inline]
ntfs_fallocate+0x59f/0x1230 fs/ntfs3/file.c:543
vfs_fallocate+0x672/0x7f0 fs/open.c:338
ioctl_preallocate fs/ioctl.c:289 [inline]
file_ioctl+0x64b/0x870 fs/ioctl.c:332
do_vfs_ioctl+0xc29/0x1540 fs/ioctl.c:576
__do_sys_ioctl fs/ioctl.c:595 [inline]
__se_sys_ioctl+0x82/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
-> #0 (mapping.invalidate_lock#3){++++}-{4:4}:
check_prev_add kernel/locking/lockdep.c:3167 [inline]
check_prevs_add kernel/locking/lockdep.c:3286 [inline]
validate_chain kernel/locking/lockdep.c:3910 [inline]
__lock_acquire+0x15a5/0x2d10 kernel/locking/lockdep.c:5239
lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870
down_read+0x97/0x200 kernel/locking/rwsem.c:1568
filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
do_page_cache_ra mm/readahead.c:349 [inline]
page_cache_ra_order+0x2b4/0x4a0 mm/readahead.c:562
do_sync_mmap_readahead+0x698/0x7b0 mm/filemap.c:3409
filemap_fault+0x790/0x13a0 mm/filemap.c:3559
__do_fault+0x138/0x2a0 mm/memory.c:5421
do_shared_fault mm/memory.c:5920 [inline]
do_fault mm/memory.c:5994 [inline]
do_pte_missing+0x65b/0x2940 mm/memory.c:4566
handle_pte_fault mm/memory.c:6375 [inline]
__handle_mm_fault mm/memory.c:6513 [inline]
handle_mm_fault+0xdc2/0x14d0 mm/memory.c:6682
do_user_addr_fault+0x75b/0x1340 arch/x86/mm/fault.c:1390
handle_page_fault arch/x86/mm/fault.c:1479 [inline]
exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1532
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
filldir64+0x2b2/0x640 fs/readdir.c:368
dir_emit include/linux/fs.h:3587 [inline]
ntfs_dir_emit fs/ntfs3/dir.c:344 [inline]
ntfs_read_hdr+0x8fb/0xc80 fs/ntfs3/dir.c:385
ntfs_readdir+0x98e/0xf40 fs/ntfs3/dir.c:545
iterate_dir+0x3a5/0x580 fs/readdir.c:110
__do_sys_getdents64 fs/readdir.c:399 [inline]
__se_sys_getdents64+0xf1/0x280 fs/readdir.c:384
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&ni->ni_lock/5);
lock(mapping.invalidate_lock#3);
lock(&ni->ni_lock/5);
rlock(mapping.invalidate_lock#3);
*** DEADLOCK ***
3 locks held by syz.4.188/6496:
#0: ffff888037dde928 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x252/0x320 fs/file.c:1260
#1: ffff88803fd78b40 (&type->i_mutex_dir_key#10){++++}-{4:4}, at: iterate_dir+0x29e/0x580 fs/readdir.c:103
#2: ffff88803fd78888 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1214 [inline]
#2: ffff88803fd78888 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_readdir+0x6c9/0xf40 fs/ntfs3/dir.c:497
stack backtrace:
CPU: 0 UID: 0 PID: 6496 Comm: syz.4.188 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2045
check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2177
check_prev_add kernel/locking/lockdep.c:3167 [inline]
check_prevs_add kernel/locking/lockdep.c:3286 [inline]
validate_chain kernel/locking/lockdep.c:3910 [inline]
__lock_acquire+0x15a5/0x2d10 kernel/locking/lockdep.c:5239
lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870
down_read+0x97/0x200 kernel/locking/rwsem.c:1568
filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
do_page_cache_ra mm/readahead.c:349 [inline]
page_cache_ra_order+0x2b4/0x4a0 mm/readahead.c:562
do_sync_mmap_readahead+0x698/0x7b0 mm/filemap.c:3409
filemap_fault+0x790/0x13a0 mm/filemap.c:3559
__do_fault+0x138/0x2a0 mm/memory.c:5421
do_shared_fault mm/memory.c:5920 [inline]
do_fault mm/memory.c:5994 [inline]
do_pte_missing+0x65b/0x2940 mm/memory.c:4566
handle_pte_fault mm/memory.c:6375 [inline]
__handle_mm_fault mm/memory.c:6513 [inline]
handle_mm_fault+0xdc2/0x14d0 mm/memory.c:6682
do_user_addr_fault+0x75b/0x1340 arch/x86/mm/fault.c:1390
handle_page_fault arch/x86/mm/fault.c:1479 [inline]
exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1532
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
RIP: 0010:filldir64+0x2b2/0x640 fs/readdir.c:369
Code: 00 48 39 c8 48 0f 47 c1 0f 01 cb 48 8b 4c 24 28 48 89 48 08 48 bd 00 00 00 00 00 fc ff df 48 8b 44 24 60 48 89 02 8b 44 24 04 <66> 89 42 10 41 80 e7 0f 44 88 7a 12 42 c6 44 2a 13 00 48 89 54 24
RSP: 0018:ffffc9000e517aa8 EFLAGS: 00050287
RAX: 0000000000000020 RBX: ffffc9000e517e38 RCX: 00000000000008c0
RDX: 0000200000000ff0 RSI: 0000000000000a29 RDI: 0000000000000a2a
RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10054a03e1 R12: ffff88802699c000
R13: 0000000000000009 R14: 0000000000000009 R15: 0000000000000008
dir_emit include/linux/fs.h:3587 [inline]
ntfs_dir_emit fs/ntfs3/dir.c:344 [inline]
ntfs_read_hdr+0x8fb/0xc80 fs/ntfs3/dir.c:385
ntfs_readdir+0x98e/0xf40 fs/ntfs3/dir.c:545
iterate_dir+0x3a5/0x580 fs/readdir.c:110
__do_sys_getdents64 fs/readdir.c:399 [inline]
__se_sys_getdents64+0xf1/0x280 fs/readdir.c:384
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7feadcacce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007feadad1e028 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007feadcd45fa0 RCX: 00007feadcacce59
RDX: 00000000000000e0 RSI: 0000200000000fc0 RDI: 0000000000000006
RBP: 00007feadcb62d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007feadcd46038 R14: 00007feadcd45fa0 R15: 00007ffebb7a32a8
</TASK>
ntfs3(loop4): failed to convert name for inode 1e.
ntfs3(loop4): ino=1f, mi_enum_attr
----------------
Code disassembly (best guess):
0: 00 48 39 add %cl,0x39(%rax)
3: c8 48 0f 47 enter $0xf48,$0x47
7: c1 0f 01 rorl $0x1,(%rdi)
a: cb lret
b: 48 8b 4c 24 28 mov 0x28(%rsp),%rcx
10: 48 89 48 08 mov %rcx,0x8(%rax)
14: 48 bd 00 00 00 00 00 movabs $0xdffffc0000000000,%rbp
1b: fc ff df
1e: 48 8b 44 24 60 mov 0x60(%rsp),%rax
23: 48 89 02 mov %rax,(%rdx)
26: 8b 44 24 04 mov 0x4(%rsp),%eax
* 2a: 66 89 42 10 mov %ax,0x10(%rdx) <-- trapping instruction
2e: 41 80 e7 0f and $0xf,%r15b
32: 44 88 7a 12 mov %r15b,0x12(%rdx)
36: 42 c6 44 2a 13 00 movb $0x0,0x13(%rdx,%r13,1)
3c: 48 rex.W
3d: 89 .byte 0x89
3e: 54 push %rsp
3f: 24 .byte 0x24
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot] [ntfs3?] possible deadlock in page_cache_ra_order
2026-05-31 2:05 [syzbot] [mm?] [fs?] possible deadlock in page_cache_ra_order syzbot
@ 2026-09-14 19:17 ` syzbot
0 siblings, 0 replies; 2+ messages in thread
From: syzbot @ 2026-09-14 19:17 UTC (permalink / raw)
To: akpm, almaz.alexandrovich, jack, linux-fsdevel, linux-kernel,
linux-mm, ntfs3, syzkaller-bugs, willy
syzbot has found a reproducer for the following issue on:
HEAD commit: 704340f1cd0d Merge tag 'x86_urgent_for_7.3-rc4' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14118df9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b454dc6b1b7acd30
dashboard link: https://syzkaller.appspot.com/bug?extid=8bd419f88e25ab12cb75
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154788c9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=134788c9580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1f812f889ad/disk-704340f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8aa4ccae83ac/vmlinux-704340f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f86a50bf181/bzImage-704340f1.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/54fd657ced87/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8bd419f88e25ab12cb75@syzkaller.appspotmail.com
ntfs3(loop1): ino=1f, mi_enum_attr
ntfs3(loop1): Mark volume as dirty due to NTFS errors
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.68/6182 is trying to acquire lock:
ffff88803364abd0 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
ffff88803364abd0 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: do_page_cache_ra mm/readahead.c:347 [inline]
ffff88803364abd0 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: page_cache_ra_order+0x2b1/0x4a0 mm/readahead.c:558
but task is already holding lock:
ffff88803364aee0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
ffff88803364aee0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_readdir+0x717/0xf70 fs/ntfs3/dir.c:541
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&ni->ni_lock/5){+.+.}-{4:4}:
__mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline]
mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:580
ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
attr_data_get_block+0x1cd/0x2c0 fs/ntfs3/attrib.c:976
ntfs_iomap_begin+0x4f0/0xf30 fs/ntfs3/inode.c:978
iomap_iter_next include/linux/iomap.h:382 [inline]
ntfs_iomap_next+0x5b6/0x880 fs/ntfs3/inode.c:2319
iomap_iter+0xe2/0xec0 fs/iomap/iter.c:122
iomap_readahead+0xa4a/0xe80 fs/iomap/buffered-io.c:751
ntfs_readahead+0x193/0x210 fs/ntfs3/inode.c:880
read_pages+0x193/0x5a0 mm/readahead.c:174
page_cache_ra_unbounded+0x679/0x8f0 mm/readahead.c:315
do_page_cache_ra mm/readahead.c:348 [inline]
page_cache_ra_order+0x2c1/0x4a0 mm/readahead.c:558
filemap_get_pages+0x493/0x1e80 mm/filemap.c:2714
filemap_read+0x429/0x11e0 mm/filemap.c:2824
__kernel_read+0x4d3/0x970 fs/read_write.c:532
integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
ima_calc_file_hash+0x45d/0x8a0 security/integrity/ima/ima_crypto.c:280
ima_collect_measurement+0x521/0xa10 security/integrity/ima/ima_api.c:300
process_measurement+0x1282/0x1c20 security/integrity/ima/ima_main.c:425
ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
security_file_post_open+0xb3/0x260 security/security.c:2755
do_open fs/namei.c:4839 [inline]
path_openat+0x148a/0x1d60 fs/namei.c:5000
do_file_open+0x23e/0x4a0 fs/namei.c:5029
do_sys_openat2+0x115/0x200 fs/open.c:1417
do_sys_open fs/open.c:1423 [inline]
__do_sys_openat fs/open.c:1439 [inline]
__se_sys_openat fs/open.c:1434 [inline]
__x64_sys_openat+0x138/0x170 fs/open.c:1434
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
-> #0 (mapping.invalidate_lock#3){.+.+}-{4:4}:
check_prev_add kernel/locking/lockdep.c:3209 [inline]
check_prevs_add kernel/locking/lockdep.c:3328 [inline]
validate_chain kernel/locking/lockdep.c:3952 [inline]
__lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
down_read+0x97/0x200 kernel/locking/rwsem.c:1574
filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
do_page_cache_ra mm/readahead.c:347 [inline]
page_cache_ra_order+0x2b1/0x4a0 mm/readahead.c:558
do_sync_mmap_readahead+0x4d6/0x7c0 mm/filemap.c:3443
filemap_fault+0x7e2/0x13c0 mm/filemap.c:3597
__do_fault+0x138/0x2a0 mm/memory.c:5565
do_shared_fault mm/memory.c:6064 [inline]
do_fault mm/memory.c:6138 [inline]
do_pte_missing+0x659/0x28f0 mm/memory.c:4700
handle_pte_fault mm/memory.c:6558 [inline]
__handle_mm_fault mm/memory.c:6707 [inline]
handle_mm_fault+0xf64/0x28c0 mm/memory.c:6876
do_user_addr_fault+0x746/0x1340 arch/x86/mm/fault.c:1394
handle_page_fault arch/x86/mm/fault.c:1483 [inline]
exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
stac arch/x86/include/asm/smap.h:-1 [inline]
filldir+0x29f/0x630 fs/readdir.c:286
dir_emit include/linux/fs.h:3607 [inline]
ntfs_dir_emit fs/ntfs3/dir.c:388 [inline]
ntfs_read_hdr+0x8a7/0xc10 fs/ntfs3/dir.c:429
ntfs_readdir+0x9ab/0xf70 fs/ntfs3/dir.c:589
iterate_dir+0x2f1/0x4e0 fs/readdir.c:110
__do_sys_getdents fs/readdir.c:319 [inline]
__se_sys_getdents+0xf1/0x270 fs/readdir.c:304
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&ni->ni_lock/5);
lock(mapping.invalidate_lock#3);
lock(&ni->ni_lock/5);
rlock(mapping.invalidate_lock#3);
*** DEADLOCK ***
locks held by syz.1.68/6182: 3, last CPU#0:
#0: ffff88803c3c2328 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x252/0x320 fs/file.c:1259
#1: ffff88803364b1a8 (&type->i_mutex_dir_key#8){++++}-{4:4}, at: iterate_dir+0x215/0x4e0 fs/readdir.c:103
#2: ffff88803364aee0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
#2: ffff88803364aee0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_readdir+0x717/0xf70 fs/ntfs3/dir.c:541
stack backtrace:
CPU: 0 UID: 0 PID: 6182 Comm: syz.1.68 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
check_prev_add kernel/locking/lockdep.c:3209 [inline]
check_prevs_add kernel/locking/lockdep.c:3328 [inline]
validate_chain kernel/locking/lockdep.c:3952 [inline]
__lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
down_read+0x97/0x200 kernel/locking/rwsem.c:1574
filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
do_page_cache_ra mm/readahead.c:347 [inline]
page_cache_ra_order+0x2b1/0x4a0 mm/readahead.c:558
do_sync_mmap_readahead+0x4d6/0x7c0 mm/filemap.c:3443
filemap_fault+0x7e2/0x13c0 mm/filemap.c:3597
__do_fault+0x138/0x2a0 mm/memory.c:5565
do_shared_fault mm/memory.c:6064 [inline]
do_fault mm/memory.c:6138 [inline]
do_pte_missing+0x659/0x28f0 mm/memory.c:4700
handle_pte_fault mm/memory.c:6558 [inline]
__handle_mm_fault mm/memory.c:6707 [inline]
handle_mm_fault+0xf64/0x28c0 mm/memory.c:6876
do_user_addr_fault+0x746/0x1340 arch/x86/mm/fault.c:1394
handle_page_fault arch/x86/mm/fault.c:1483 [inline]
exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
RIP: 0010:filldir+0x29f/0x630 fs/readdir.c:288
Code: df 49 29 ef 48 b8 00 f0 ff ff ff 7f 00 00 49 39 c7 4c 0f 47 f8 bf 07 00 00 00 44 89 f6 e8 e9 35 7f ff 0f 01 cb 48 8b 44 24 20 <49> 89 47 08 48 bd 00 00 00 00 00 fc ff df 48 8b 44 24 40 48 89 03
RSP: 0018:ffffc90004cf7ab0 EFLAGS: 00050293
RAX: 00000000000009e8 RBX: 0000200000002050 RCX: ffff888026543e80
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000007
RBP: 0000000000000020 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed1004ca87d1 R12: ffff88803ae8a000
R13: 0000000000000005 R14: 0000000000000005 R15: 0000200000002030
dir_emit include/linux/fs.h:3607 [inline]
ntfs_dir_emit fs/ntfs3/dir.c:388 [inline]
ntfs_read_hdr+0x8a7/0xc10 fs/ntfs3/dir.c:429
ntfs_readdir+0x9ab/0xf70 fs/ntfs3/dir.c:589
iterate_dir+0x2f1/0x4e0 fs/readdir.c:110
__do_sys_getdents fs/readdir.c:319 [inline]
__se_sys_getdents+0xf1/0x270 fs/readdir.c:304
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe25947e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe258a9c028 EFLAGS: 00000246 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00007fe259706180 RCX: 00007fe25947e159
RDX: 0000000020002078 RSI: 0000200000001fc0 RDI: 0000000000000007
RBP: 00007fe25951503b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe259706218 R14: 00007fe259706180 R15: 00007ffeaad84d78
</TASK>
ntfs3(loop1): ino=1f, mi_enum_attr
----------------
Code disassembly (best guess):
0: df 49 29 fisttps 0x29(%rcx)
3: ef out %eax,(%dx)
4: 48 b8 00 f0 ff ff ff movabs $0x7ffffffff000,%rax
b: 7f 00 00
e: 49 39 c7 cmp %rax,%r15
11: 4c 0f 47 f8 cmova %rax,%r15
15: bf 07 00 00 00 mov $0x7,%edi
1a: 44 89 f6 mov %r14d,%esi
1d: e8 e9 35 7f ff call 0xff7f360b
22: 0f 01 cb stac
25: 48 8b 44 24 20 mov 0x20(%rsp),%rax
* 2a: 49 89 47 08 mov %rax,0x8(%r15) <-- trapping instruction
2e: 48 bd 00 00 00 00 00 movabs $0xdffffc0000000000,%rbp
35: fc ff df
38: 48 8b 44 24 40 mov 0x40(%rsp),%rax
3d: 48 89 03 mov %rax,(%rbx)
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-14 19:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-05-31 2:05 [syzbot] [mm?] [fs?] possible deadlock in page_cache_ra_order syzbot
2026-09-14 19:17 ` [syzbot] [ntfs3?] " syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®