[moderation] [fs?] [mm?] BUG: unable to handle kernel NULL pointer dereference in folio_mark_dirty (2)

0 views
Skip to first unread message

syzbot

unread,
Jun 19, 2024, 7:17:23 AM (10 days ago) Jun 19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2ccbdf43d5e7 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17ccd851980000
kernel config: https://syzkaller.appspot.com/x/.config?x=81c0d76ceef02b39
dashboard link: https://syzkaller.appspot.com/bug?extid=bb2bd9900b1a3b7d4c78
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org wi...@infradead.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2ccbdf43.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/13cdb5bfbafa/vmlinux-2ccbdf43.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a14f5d07f81/bzImage-2ccbdf43.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bb2bd9...@syzkaller.appspotmail.com

ntfs3: loop0: Different NTFS sector size (2048) and media sector size (512).
ntfs3: loop0: 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 26be3067 P4D 26be3067 PUD 46663067 PMD 0
Oops: Oops: 0010 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 11204 Comm: syz-executor.0 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000c59f6e8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88802a053818 RCX: ffffc90002cf1000
RDX: 1ffffffff16c77ff RSI: ffffea000179c680 RDI: ffff88802a053818
RBP: ffffffff8b63bfe0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000017 R12: ffffea000179c680
R13: ffffea000179c680 R14: ffffea000179c680 R15: ffff88802a0533a0
FS: 0000000000000000(0000) GS:ffff88802c200000(0063) knlGS:00000000f5f01b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000267e2000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
folio_mark_dirty+0xce/0x150 mm/page-writeback.c:2860
attr_make_nonresident+0x930/0xf50 fs/ntfs3/attrib.c:301
attr_set_size_res fs/ntfs3/attrib.c:371 [inline]
attr_set_size+0x124b/0x2b90 fs/ntfs3/attrib.c:432
ntfs_set_size+0x13d/0x220 fs/ntfs3/inode.c:851
ntfs_extend+0x401/0x570 fs/ntfs3/file.c:335
ntfs_file_write_iter+0x433/0x2050 fs/ntfs3/file.c:1124
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x6b6/0x1140 fs/read_write.c:590
ksys_write+0x12f/0x260 fs/read_write.c:643
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf730f579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f5f015ac EFLAGS: 00000292 ORIG_RAX: 0000000000000004
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000000020000140
RDX: 000000000000fcb8 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000c59f6e8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88802a053818 RCX: ffffc90002cf1000
RDX: 1ffffffff16c77ff RSI: ffffea000179c680 RDI: ffff88802a053818
RBP: ffffffff8b63bfe0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000017 R12: ffffea000179c680
R13: ffffea000179c680 R14: ffffea000179c680 R15: ffff88802a0533a0
FS: 0000000000000000(0000) GS:ffff88802c200000(0063) knlGS:00000000f5f01b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000267e2000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 10 06 adc %al,(%rsi)
2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi
6: 10 07 adc %al,(%rdi)
8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi
c: 10 08 adc %cl,(%rax)
e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi
1e: 00 51 52 add %dl,0x52(%rcx)
21: 55 push %rbp
22: 89 e5 mov %esp,%ebp
24: 0f 34 sysenter
26: cd 80 int $0x80
* 28: 5d pop %rbp <-- trapping instruction
29: 5a pop %rdx
2a: 59 pop %rcx
2b: c3 ret
2c: 90 nop
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi


---
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.

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
Reply all
Reply to author
Forward
0 new messages