kernel BUG in ext4_ind_remove_space

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 21ad423fe521 Linux 4.14.265
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=167914a4700000
kernel config: https://syzkaller.appspot.com/x/.config?x=f79494e54ef9cb67
dashboard link: https://syzkaller.appspot.com/bug?extid=227839a33b4efda3cafd
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12eed2c2700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124af108700000

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

audit: type=1800 audit(1644407705.577:2): pid=7974 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor333" name="bus" dev="sda1" ino=13861 res=0
EXT4-fs warning (device sda1): ext4_block_to_path:105: block 1074791436 > max in inode 13861
------------[ cut here ]------------
kernel BUG at fs/ext4/indirect.c:1236!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 7974 Comm: syz-executor333 Not tainted 4.14.265-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809c2f6140 task.stack: ffff888091668000
RIP: 0010:ext4_ind_remove_space+0xe47/0x1250 fs/ext4/indirect.c:1236
RSP: 0018:ffff88809166fb20 EFLAGS: 00010297
RAX: ffff88809c2f6140 RBX: 000000004010040c RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bbcc0 RDI: ffffed10122cdf31
RBP: 0000000000001000 R08: 000000000000005c R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88809166fbd0
R13: 0000000000000003 R14: 000000004010040c R15: ffff88808e935730
FS: 00005555563c3300(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020400002 CR3: 00000000abf79000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_punch_hole+0xcf4/0x1000 fs/ext4/inode.c:4318
ext4_fallocate+0x327/0x1d80 fs/ext4/extents.c:4968
vfs_fallocate+0x346/0x790 fs/open.c:319
SYSC_fallocate fs/open.c:342 [inline]
SyS_fallocate+0x4a/0x80 fs/open.c:336
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f4c5f1930d9
RSP: 002b:00007fffb5cdd4a8 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4c5f1930d9
RDX: 0000000001000000 RSI: 0000000000000003 RDI: 0000000000000005
RBP: 00007f4c5f1570c0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000ffeffeff000 R11: 0000000000000246 R12: 00007f4c5f157150
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Code: 01 00 0f 85 4c 03 00 00 48 8b 0b 4c 89 fe 44 8b 4c 24 20 48 8b 7c 24 10 48 83 c1 04 e8 73 bd ff ff e9 f5 f6 ff ff e8 79 45 9c ff <0f> 0b e8 72 45 9c ff 48 8b 7c 24 10 31 d2 4c 89 fe 8b 84 24 b0
RIP: ext4_ind_remove_space+0xe47/0x1250 fs/ext4/indirect.c:1236 RSP: ffff88809166fb20
---[ end trace 48a577c924040e25 ]---


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches