WARNING in iomap_dio_actor

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a1b5c7880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=9fa1ac403a0ecf030fca
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

audit: type=1804 audit(1670808498.061:3163): pid=4172 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir3526296885/syzkaller.FafT1M/250/file0/bus" dev="loop4" ino=41 res=1
audit: type=1804 audit(1670808498.121:3164): pid=4179 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir680431241/syzkaller.muI7Y1/276/file0/bus" dev="loop5" ino=41 res=1
WARNING: CPU: 0 PID: 4172 at fs/iomap.c:1800 iomap_dio_actor+0x2e5/0x4e0 fs/iomap.c:1800
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 4172 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:iomap_dio_actor+0x2e5/0x4e0 fs/iomap.c:1800
Code: 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 ba 01 00 00 49 01 5c 24 18 e9 b9 fd ff ff e8 7b 00 a5 ff <0f> 0b 49 c7 c5 fb ff ff ff e9 a6 fd ff ff e8 68 00 a5 ff 49 8d 7c
RSP: 0018:ffff888045cdf680 EFLAGS: 00010206
RAX: 0000000000040000 RBX: ffff888045cdf738 RCX: ffffc90009160000
RDX: 00000000000105b0 RSI: ffffffff81bd84f5 RDI: 0000000000000003
RBP: 0000000000001000 R08: ffff888045cdf738 R09: 0000000000000005
R10: 0000000000000003 R11: ffffffff8c66501b R12: ffff8880945d2180
R13: 0000000000001000 R14: ffff8880131e4360 R15: 0000000000000002
iomap_apply+0x18b/0x290 fs/iomap.c:87
iomap_dio_rw+0x8cc/0xed0 fs/iomap.c:1909
xfs_file_dio_aio_read+0x185/0x4a0 fs/xfs/xfs_file.c:195
xfs_file_read_iter+0x3dc/0x4e0 fs/xfs/xfs_file.c:268
call_read_iter include/linux/fs.h:1815 [inline]
generic_file_splice_read+0x44a/0x6d0 fs/splice.c:308
do_splice_to+0x10e/0x160 fs/splice.c:881
splice_direct_to_actor+0x2b9/0x8d0 fs/splice.c:959
do_splice_direct+0x1a7/0x270 fs/splice.c:1068
do_sendfile+0x550/0xc30 fs/read_write.c:1447
__do_sys_sendfile64 fs/read_write.c:1508 [inline]
__se_sys_sendfile64+0x147/0x160 fs/read_write.c:1494
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f28e0bcd0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f28df13f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f28e0cecf80 RCX: 00007f28e0bcd0d9
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000005
RBP: 00007f28e0c28ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 000001ffffffe100 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd6c42b8bf R14: 00007f28df13f300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..


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