==================================================================
BUG: KCSAN: data-race in ext4_mark_iloc_dirty / ext4_orphan_del

write to 0xffff8881049b995c of 4 bytes by task 16981 on cpu 0:
 ext4_orphan_del+0x579/0x730 fs/ext4/orphan.c:296
 ext4_truncate+0x8b6/0xa80 fs/ext4/inode.c:4224
 ext4_truncate_failed_write fs/ext4/truncate.h:22 [inline]
 ext4_handle_inode_extension fs/ext4/file.c:358 [inline]
 ext4_dio_write_iter fs/ext4/file.c:574 [inline]
 ext4_file_write_iter+0xcf4/0x11f0 fs/ext4/file.c:678
 call_write_iter include/linux/fs.h:2163 [inline]
 io_write fs/io_uring.c:3638 [inline]
 io_issue_sqe+0x1c82/0x67b0 fs/io_uring.c:6656
 io_wq_submit_work+0xf5/0x2c0 fs/io_uring.c:6800
 io_worker_handle_work+0x788/0xa20 fs/io-wq.c:515
 io_wqe_worker+0x1b9/0x540 fs/io-wq.c:566
 ret_from_fork+0x1f/0x30

read to 0xffff8881049b995c of 4 bytes by task 17091 on cpu 1:
 ext4_do_update_inode fs/ext4/inode.c:5029 [inline]
 ext4_mark_iloc_dirty+0x87c/0x1700 fs/ext4/inode.c:5683
 __ext4_mark_inode_dirty+0x4ec/0x5c0 fs/ext4/inode.c:5879
 __ext4_ext_dirty fs/ext4/extents.c:170 [inline]
 ext4_ext_rm_leaf+0x82d/0xd40 fs/ext4/extents.c:2708
 ext4_ext_remove_space+0x8f6/0x12b0 fs/ext4/extents.c:2920
 ext4_ext_truncate+0xfe/0x170 fs/ext4/extents.c:4382
 ext4_truncate+0x76e/0xa80 fs/ext4/inode.c:4204
 ext4_truncate_failed_write fs/ext4/truncate.h:22 [inline]
 ext4_handle_inode_extension fs/ext4/file.c:358 [inline]
 ext4_dio_write_iter fs/ext4/file.c:574 [inline]
 ext4_file_write_iter+0xcf4/0x11f0 fs/ext4/file.c:678
 call_write_iter include/linux/fs.h:2163 [inline]
 io_write fs/io_uring.c:3638 [inline]
 io_issue_sqe+0x1c82/0x67b0 fs/io_uring.c:6656
 io_wq_submit_work+0xf5/0x2c0 fs/io_uring.c:6800
 io_worker_handle_work+0x788/0xa20 fs/io-wq.c:515
 io_wqe_worker+0x1b9/0x540 fs/io-wq.c:566
 ret_from_fork+0x1f/0x30

value changed: 0x00000518 -> 0x000004f3

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 17091 Comm: iou-wrk-16985 Not tainted 5.15.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================