[syzbot] [ntfs3?] general protection fault in al_destroy
syzbot <[email protected]>
| Newsgroups | dev.linux.lists.ntfs3,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hello, syzbot found the following issue on: HEAD commit: 6b8c8af514d7 Add linux-next specific files for 20260807 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=13210149580000 kernel config: https://syzkaller.appspot.com/x/.config?x=6d343b54cc50df0f dashboard link: https://syzkaller.appspot.com/bug?extid=04cf7b83f6dd2c3a54c8 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=1284c2c6580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/71ff4edcb608/disk-6b8c8af5.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1f5fa331d8f2/vmlinux-6b8c8af5.xz kernel image: https://storage.googleapis.com/syzbot-assets/f993558ec63b/bzImage-6b8c8af5.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/f8133373f34e/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] option from the mount to silence this warning. ======================================================= ntfs3(loop0): Different NTFS sector size (1024) and media sector size (512). Oops: general protection fault, probably for non-canonical address 0xdffffc0000000042: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000210-0x0000000000000217] CPU: 1 UID: 0 PID: 5838 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 RIP: 0010:run_close fs/ntfs3/ntfs_fs.h:1034 [inline] RIP: 0010:al_destroy+0x49/0xc0 fs/ntfs3/attrlist.c:33 Code: 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 58 8d 08 ff 48 8b 1b 4c 8d b3 10 02 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 38 8d 08 ff 48 8b bb 10 02 00 00 RSP: 0018:ffffc9000348f960 EFLAGS: 00010206 RAX: 0000000000000042 RBX: 0000000000000000 RCX: ffff88802ac23e80 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88805a8d7810 RBP: 0000000000000001 R08: ffffffff9058fb7f R09: 1ffffffff20b1f6f R10: dffffc0000000000 R11: fffffbfff20b1f70 R12: ffff88805a8d7a60 R13: dffffc0000000000 R14: 0000000000000210 R15: dffffc0000000000 FS: 000055555d771500(0000) GS:ffff88812500c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6813d4c000 CR3: 000000007270e000 CR4: 00000000003526f0 Call Trace: <TASK> ni_clear+0x5d/0x630 fs/ntfs3/frecord.c:110 evict+0x624/0xb50 fs/inode.c:822 ntfs_new_inode+0x8c/0x120 fs/ntfs3/fsntfs.c:1719 ntfs_create_inode+0x6e7/0x3420 fs/ntfs3/inode.c:1520 ntfs_mkdir+0x37/0x50 fs/ntfs3/namei.c:234 vfs_mkdir+0x40c/0x620 fs/namei.c:5410 filename_mkdirat+0x285/0x510 fs/namei.c:5443 __do_sys_mkdirat fs/namei.c:5464 [inline] __se_sys_mkdirat+0x35/0x150 fs/namei.c:5461 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f057a79cf47 Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 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:00007fff0d960bd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007fff0d960c60 RCX: 00007f057a79cf47 RDX: 00000000000001ff RSI: 00002000000000c0 RDI: 00000000ffffff9c RBP: 00002000000002c0 R08: 00002000000007c0 R09: 0000000000000000 R10: 00002000000002c0 R11: 0000000000000246 R12: 00002000000000c0 R13: 00007fff0d960c20 R14: 0000000000000000 R15: 0000000000000000 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:run_close fs/ntfs3/ntfs_fs.h:1034 [inline] RIP: 0010:al_destroy+0x49/0xc0 fs/ntfs3/attrlist.c:33 Code: 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 58 8d 08 ff 48 8b 1b 4c 8d b3 10 02 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 38 8d 08 ff 48 8b bb 10 02 00 00 RSP: 0018:ffffc9000348f960 EFLAGS: 00010206 RAX: 0000000000000042 RBX: 0000000000000000 RCX: ffff88802ac23e80 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88805a8d7810 RBP: 0000000000000001 R08: ffffffff9058fb7f R09: 1ffffffff20b1f6f R10: dffffc0000000000 R11: fffffbfff20b1f70 R12: ffff88805a8d7a60 R13: dffffc0000000000 R14: 0000000000000210 R15: dffffc0000000000 FS: 000055555d771500(0000) GS:ffff88812500c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f6813d4c000 CR3: 000000007270e000 CR4: 00000000003526f0 ---------------- Code disassembly (best guess): 0: 02 00 add (%rax),%al 2: 00 48 89 add %cl,-0x77(%rax) 5: d8 48 c1 fmuls -0x3f(%rax) 8: e8 03 42 80 3c call 0x3c804210 d: 38 00 cmp %al,(%rax) f: 74 08 je 0x19 11: 48 89 df mov %rbx,%rdi 14: e8 58 8d 08 ff call 0xff088d71 19: 48 8b 1b mov (%rbx),%rbx 1c: 4c 8d b3 10 02 00 00 lea 0x210(%rbx),%r14 23: 4c 89 f0 mov %r14,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction 2f: 74 08 je 0x39 31: 4c 89 f7 mov %r14,%rdi 34: e8 38 8d 08 ff call 0xff088d71 39: 48 8b bb 10 02 00 00 mov 0x210(%rbx),%rdi --- 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 [email protected]. 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 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. 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