[Linux-ntfs-dev] [syzbot] [ntfs?] kernel BUG in ntfs_end_buffer_async_read

[syzbot <syz...@sy...>]

Hello,

syzbot found the following issue on:

HEAD commit:    fe15c26ee26e Linux 6.3-rc1
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=12feadbcc80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7573cbcd881a88c9
dashboard link: https://syzkaller.appspot.com/bug?extid=72ba5fe5556d82ad118b
compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/89d41abd07bd/disk-fe15c26e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa75f5030ade/vmlinux-fe15c26e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/590d0f5903ee/Image-fe15c26e.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syz...@sy...

------------[ cut here ]------------
kernel BUG at fs/ntfs/aops.c:130!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.3.0-rc1-syzkaller-gfe15c26ee26e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ntfs_end_buffer_async_read+0xa28/0xb78 fs/ntfs/aops.c:130
lr : ntfs_end_buffer_async_read+0xa28/0xb78 fs/ntfs/aops.c:130
sp : ffff80001a477a30
x29: ffff80001a477a50 x28: ffff0001416534a0 x27: 0000000000000019
x26: dfff800000000000 x25: 0000000000001000 x24: ffff00013f9ed3a0
x23: 0000000000000000 x22: ffff00013f9ed6c0 x21: 0000000000000001
x20: 0000000000020211 x19: 0000000000000330 x18: 1fffe000368995b6
x17: ffff800015cdd000 x16: ffff80000826e470 x15: 0000000000000000
x14: 1ffff00002b9c0b2 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000965190c x10: 0000000000000000 x9 : ffff80000965190c
x8 : ffff0000c0af1b40 x7 : ffff800009651140 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff80001a477940 x1 : 0000000000020211 x0 : 0000000000001000
Call trace:
 ntfs_end_buffer_async_read+0xa28/0xb78 fs/ntfs/aops.c:130
 end_bio_bh_io_sync+0xb0/0x194 fs/buffer.c:2703
 bio_endio+0x940/0x984 block/bio.c:1607
 req_bio_endio block/blk-mq.c:795 [inline]
 blk_update_request+0x444/0xdc0 block/blk-mq.c:927
 blk_mq_end_request+0x54/0x88 block/blk-mq.c:1054
 lo_complete_rq+0x140/0x258 drivers/block/loop.c:370
 blk_complete_reqs block/blk-mq.c:1132 [inline]
 blk_done_softirq+0x11c/0x168 block/blk-mq.c:1137
 __do_softirq+0x378/0xfbc kernel/softirq.c:571
 run_ksoftirqd+0x6c/0x148 kernel/softirq.c:934
 smpboot_thread_fn+0x4b0/0x96c kernel/smpboot.c:164
 kthread+0x24c/0x2d4 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: c8097e88 35ffffa9 17fffdb3 97bafdea (d4210000) 
---[ end trace 0000000000000000 ]---


---
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 syz...@go....

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.