[syzbot] BUG: unable to handle kernel paging request in mi_enum_attr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

syzbot found the following issue on:

HEAD commit:    a41a877bc12d Merge branch 'for-next/fixes' into for-kernelci
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=11d7f5ad080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5cea15779c42821c
dashboard link: https://syzkaller.appspot.com/bug?extid=28207acc70bbf3d85b74
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+28207acc70bbf3d85b74@xxxxxxxxxxxxxxxxxxxxxxxxx

Unable to handle kernel paging request at virtual address ffff000224d7f83a
Mem abort info:
  ESR = 0x0000000096000005
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x05: level 1 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000005
  CM = 0, WnR = 0
swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000001c5736000
[ffff000224d7f83a] pgd=180000023fff8003, p4d=180000023fff8003, pud=0000000000000000
Internal error: Oops: 96000005 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 28529 Comm: syz-executor.3 Not tainted 6.0.0-rc2-syzkaller-16455-ga41a877bc12d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : mi_enum_attr+0x10c/0x314 fs/ntfs3/record.c:227
lr : mi_enum_attr+0xf0/0x314 fs/ntfs3/record.c:223
sp : ffff8000220f3940
x29: ffff8000220f3940 x28: ffff000124d7f800 x27: ffff000124d7f838
x26: 00000000fffffffe x25: 0000000000000048 x24: 0000000000000000
x23: 0000000000000000 x22: 0000000000000036 x21: 0000000000000198
x20: 0000000000000038 x19: ffff000224d7f836 x18: 0000000000000002
x17: ffff80000c04d6bc x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000064 x13: 0000000000989680 x12: 0000000000040000
x11: 00000000000105f8 x10: ffff800019725000 x9 : ffff800008c10880
x8 : 00000000000105f9 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff000124d7fc00 x4 : ffff00011eb5e400 x3 : 0000000000000000
x2 : ffff8000220f3a70 x1 : 00000000fffffffe x0 : 0000000000000018
Call trace:
 mi_enum_attr+0x10c/0x314 fs/ntfs3/record.c:210
 ni_enum_attr_ex+0x174/0x29c fs/ntfs3/frecord.c:259
 ntfs_read_mft fs/ntfs3/inode.c:114 [inline]
 ntfs_iget5+0xf44/0x138c fs/ntfs3/inode.c:501
 ntfs_loadlog_and_replay+0x98/0x1ec fs/ntfs3/fsntfs.c:272
 ntfs_fill_super+0xc10/0x14a4 fs/ntfs/super.c:2904
 get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
 ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1358
 vfs_get_tree+0x40/0x140 fs/super.c:1530
 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
 path_mount+0x358/0x914 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
 el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x48/0x154 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:624
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:642
 el0t_64_sync+0x18c/0x190
Code: 97da4c0f 14000039 97da4c0d 8b160293 (b9400674) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	97da4c0f 	bl	0xffffffffff69303c
   4:	14000039 	b	0xe8
   8:	97da4c0d 	bl	0xffffffffff69303c
   c:	8b160293 	add	x19, x20, x22
* 10:	b9400674 	ldr	w20, [x19, #4] <-- trapping instruction


---
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 syzkaller@xxxxxxxxxxxxxxxx.

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




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux