==================================================================
BUG: KCSAN: data-race in process_one_work / process_one_work

read-write to 0xffff888100066098 of 8 bytes by task 9433 on cpu 0:
 process_one_work+0x40d/0x860 kernel/workqueue.c:2598
 worker_thread+0x5f2/0xa10 kernel/workqueue.c:2751
 kthread+0x1d7/0x210 kernel/kthread.c:389
 ret_from_fork+0x2e/0x40 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

read-write to 0xffff888100066098 of 8 bytes by task 4426 on cpu 1:
 process_one_work+0x40d/0x860 kernel/workqueue.c:2598
 worker_thread+0x5f2/0xa10 kernel/workqueue.c:2751
 kthread+0x1d7/0x210 kernel/kthread.c:389
 ret_from_fork+0x2e/0x40 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

value changed: 0x0000000000003a6b -> 0x0000000000003a70

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4426 Comm: kworker/u4:6 Not tainted 6.5.0-rc7-syzkaller-00013-g53663f4103ff #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events_unbound flush_to_ldisc
==================================================================
EXT4-fs error (device loop5): ext4_mb_generate_buddy:1216: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters
EXT4-fs (loop5): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 2048 with error 28
EXT4-fs (loop5): This should not happen!! Data will be lost

EXT4-fs (loop5): Total free blocks count 0
EXT4-fs (loop5): Free/Dirty block details
EXT4-fs (loop5): free_blocks=2415919104
EXT4-fs (loop5): dirty_blocks=8192
EXT4-fs (loop5): Block reservation details
EXT4-fs (loop5): i_reserved_data_blocks=512
EXT4-fs (loop5): Delayed block allocation failed for inode 18 at logical offset 2050 with max blocks 2048 with error 28