[moderation] [ntfs3?] BUG: unable to handle kernel paging request in ntfs_iget5

0 views
Skip to first unread message

syzbot

unread,
May 16, 2024, 12:43:26 PMMay 16
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cf87f46fd34d Merge tag 'drm-fixes-2024-05-11' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=172e743f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7144b4fe7fbf5900
dashboard link: https://syzkaller.appspot.com/bug?extid=2b11d9b8850e1b3f6a1b
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [almaz.ale...@paragon-software.com linux-...@vger.kernel.org nt...@lists.linux.dev]

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-cf87f46f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6c900001042d/vmlinux-cf87f46f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1859ec0cb9be/bzImage-cf87f46f.xz

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

loop3: detected capacity change from 0 to 4096
ntfs3: loop3: Different NTFS sector size (2048) and media sector size (512).
ntfs3: loop3: Mark volume as dirty due to NTFS errors
BUG: unable to handle page fault for address: ffffc90004030f89
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 15000067 P4D 15000067 PUD 15ee6067 PMD 1d3f8067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 7683 Comm: syz-executor.3 Not tainted 6.9.0-rc7-syzkaller-00183-gcf87f46fd34d #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:ntfs_read_mft fs/ntfs3/inode.c:72 [inline]
RIP: 0010:ntfs_iget5+0x4c8/0x3950 fs/ntfs3/inode.c:538
Code: 24 08 31 ff 4c 89 ee e8 86 dc ba fe 48 8b 7c 24 20 4d 85 ed 0f 94 84 24 ae 00 00 00 40 0f 94 c6 40 0f b6 f6 e8 c9 f8 01 00 31 <ff> 41 89 c4 89 c6 e8 2d dc ba fe 45 85 e4 0f 85 70 01 00 00 e8 3f
RSP: 0018:ffffc9000372f898 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc9000372fa50 RCX: ffffc90004031000
RDX: 0000000000040000 RSI: ffffffff82d4e7d0 RDI: 0000000000000004
RBP: 1ffff920006e5f2b R08: 0000000000000004 R09: 0000000000000800
R10: 0000000000000800 R11: 0000000000000001 R12: 0000000000000000
R13: 000000000000000b R14: ffff8880122c4000 R15: ffff88804b893d50
FS: 00007fe0515086c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90004030f89 CR3: 000000004deea000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ntfs_extend_init+0xf4/0x560 fs/ntfs3/fsntfs.c:224
ntfs_fill_super+0x3a0b/0x4490 fs/ntfs3/super.c:1537
get_tree_bdev+0x36f/0x610 fs/super.c:1614
vfs_get_tree+0x8f/0x380 fs/super.c:1779
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe05087f46a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe051507ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fe051507f80 RCX: 00007fe05087f46a
RDX: 0000000020000000 RSI: 0000000020000200 RDI: 00007fe051507f40
RBP: 0000000020000000 R08: 00007fe051507f80 R09: 0000000003204080
R10: 0000000003204080 R11: 0000000000000202 R12: 0000000020000200
R13: 00007fe051507f40 R14: 000000000001f456 R15: 00000000200000c0
</TASK>
Modules linked in:
CR2: ffffc90004030f89
---[ end trace 0000000000000000 ]---
RIP: 0010:ntfs_read_mft fs/ntfs3/inode.c:72 [inline]
RIP: 0010:ntfs_iget5+0x4c8/0x3950 fs/ntfs3/inode.c:538
Code: 24 08 31 ff 4c 89 ee e8 86 dc ba fe 48 8b 7c 24 20 4d 85 ed 0f 94 84 24 ae 00 00 00 40 0f 94 c6 40 0f b6 f6 e8 c9 f8 01 00 31 <ff> 41 89 c4 89 c6 e8 2d dc ba fe 45 85 e4 0f 85 70 01 00 00 e8 3f
RSP: 0018:ffffc9000372f898 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc9000372fa50 RCX: ffffc90004031000
RDX: 0000000000040000 RSI: ffffffff82d4e7d0 RDI: 0000000000000004
RBP: 1ffff920006e5f2b R08: 0000000000000004 R09: 0000000000000800
R10: 0000000000000800 R11: 0000000000000001 R12: 0000000000000000
R13: 000000000000000b R14: ffff8880122c4000 R15: ffff88804b893d50
FS: 00007fe0515086c0(0000) GS:ffff88806b200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90004030f89 CR3: 000000004deea000 CR4: 0000000000352ef0
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.

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