general protection fault in ntfs_set_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 53e99dcff61e Merge tag 'soc-fixes-6.0-rc4' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10cf4015080000
kernel config: https://syzkaller.appspot.com/x/.config?x=f4d613baa509128c
dashboard link: https://syzkaller.appspot.com/bug?extid=94c4874e2b5c44080732
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
CC: [almaz.ale...@paragon-software.com linux-...@vger.kernel.org ll...@lists.linux.dev nat...@kernel.org ndesau...@google.com nt...@lists.linux.dev tr...@redhat.com]

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+94c487...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc000de79052: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x000000006f3c8290-0x000000006f3c8297]
CPU: 0 PID: 17934 Comm: syz-executor.0 Not tainted 6.0.0-rc4-syzkaller-00055-g53e99dcff61e #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:ntfs_set_inode+0x4a/0x70 fs/ntfs3/inode.c:485
Code: 14 02 48 89 d8 83 e0 07 83 c0 03 38 d0 7c 04 84 d2 75 26 48 8d 7d 40 8b 1b 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 13 48 89 5d 40 31 c0 5b 5d c3 48 89 df e8 6f 2e 20
RSP: 0018:ffffc90006387968 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 000000000000000a RCX: ffffc9000491a000
RDX: 000000000de79052 RSI: ffffffff82a83b3d RDI: 000000006f3c8290
RBP: 000000006f3c8250 R08: 0000000000000001 R09: 0000000000000003
R10: fffff52000c70f21 R11: 0000000000000000 R12: ffffc90006387cb0
R13: ffffffff82a83b2f R14: 0000000000000000 R15: ffff88806f3c8278
FS: 0000000000000000(0000) GS:ffff88802c800000(0063) knlGS:00000000f7f70b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000030a23000 CR3: 000000006f915000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 00000000d08e000a
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
log_replay+0xf780/0xf780
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ntfs_set_inode+0x4a/0x70 fs/ntfs3/inode.c:485
Code: 14 02 48 89 d8 83 e0 07 83 c0 03 38 d0 7c 04 84 d2 75 26 48 8d 7d 40 8b 1b 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 13 48 89 5d 40 31 c0 5b 5d c3 48 89 df e8 6f 2e 20
RSP: 0018:ffffc90006387968 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 000000000000000a RCX: ffffc9000491a000
RDX: 000000000de79052 RSI: ffffffff82a83b3d RDI: 000000006f3c8290
RBP: 000000006f3c8250 R08: 0000000000000001 R09: 0000000000000003
R10: fffff52000c70f21 R11: 0000000000000000 R12: ffffc90006387cb0
R13: ffffffff82a83b2f R14: 0000000000000000 R15: ffff88806f3c8278
FS: 0000000000000000(0000) GS:ffff88802c800000(0063) knlGS:00000000f7f70b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000030a23000 CR3: 000000006f915000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 00000000d08e000a
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 14 02 adc $0x2,%al
2: 48 89 d8 mov %rbx,%rax
5: 83 e0 07 and $0x7,%eax
8: 83 c0 03 add $0x3,%eax
b: 38 d0 cmp %dl,%al
d: 7c 04 jl 0x13
f: 84 d2 test %dl,%dl
11: 75 26 jne 0x39
13: 48 8d 7d 40 lea 0x40(%rbp),%rdi
17: 8b 1b mov (%rbx),%ebx
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 75 13 jne 0x43
30: 48 89 5d 40 mov %rbx,0x40(%rbp)
34: 31 c0 xor %eax,%eax
36: 5b pop %rbx
37: 5d pop %rbp
38: c3 retq
39: 48 89 df mov %rbx,%rdi
3c: e8 .byte 0xe8
3d: 6f outsl %ds:(%rsi),(%dx)
3e: 2e cs
3f: 20 .byte 0x20


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

[syzbot]

Sending this report upstream.