Hello,
syzbot found the following issue on:
HEAD commit: 6449a0ba6843 Linux 6.1.19
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14a747ccc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9ed8b3ec03e8c126
dashboard link:
https://syzkaller.appspot.com/bug?extid=f3e5d0948a1837ed1bb0
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/0ad616da3180/disk-6449a0ba.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/42677a30acb3/vmlinux-6449a0ba.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2e21fe35d03d/bzImage-6449a0ba.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f3e5d0...@syzkaller.appspotmail.com
ntfs3: loop2: Mark volume as dirty due to NTFS errors
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 28a5f067 P4D 28a5f067 PUD 702f7067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 10553 Comm: syz-executor.2 Not tainted 6.1.19-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc900055dfcc8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffea0001283380 RCX: dffffc0000000000
RDX: ffffc9000b0c1000 RSI: ffffea0001283380 RDI: ffff888070f38478
RBP: 0000000000000000 R08: ffffffff81b9f6e6 R09: fffff94000250671
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000001000
R13: 0000000000000000 R14: 0000000000001000 R15: ffffffffffffffff
FS: 00007f52922d3700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000001dc7b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ntfs_sparse_cluster+0x718/0xa20 fs/ntfs3/file.c:335
ntfs_fallocate+0xa70/0x1020 fs/ntfs3/file.c:727
vfs_fallocate+0x547/0x6b0 fs/open.c:323
ksys_fallocate fs/open.c:346 [inline]
__do_sys_fallocate fs/open.c:354 [inline]
__se_sys_fallocate fs/open.c:352 [inline]
__x64_sys_fallocate+0xb9/0x100 fs/open.c:352
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f529148c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f52922d3168 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f52915abf80 RCX: 00007f529148c0f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f52914e7b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff0f9317cf R14: 00007f52922d3300 R15: 0000000000022000
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc900055dfcc8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffea0001283380 RCX: dffffc0000000000
RDX: ffffc9000b0c1000 RSI: ffffea0001283380 RDI: ffff888070f38478
RBP: 0000000000000000 R08: ffffffff81b9f6e6 R09: fffff94000250671
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000001000
R13: 0000000000000000 R14: 0000000000001000 R15: ffffffffffffffff
FS: 00007f52922d3700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000001dc7b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.