[moderation] [mm?] [fs?] upstream test error: KCSAN: data-race in __xa_clear_mark / xas_find_marked (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b6ea1680d0ac Merge tag 'v6.15-p6' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=136dd774580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6bd11c5d4ce102b4
dashboard link: https://syzkaller.appspot.com/bug?extid=059bc69d4ad4a1169f0b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org wi...@infradead.org]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d159f4383791/disk-b6ea1680.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6180a7b17173/vmlinux-b6ea1680.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84888c389237/bzImage-b6ea1680.xz

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

==================================================================
BUG: KCSAN: data-race in __xa_clear_mark / xas_find_marked

read-write to 0xffff888106ce1900 of 8 bytes by task 37 on cpu 0:
instrument_read_write include/linux/instrumented.h:55 [inline]
__instrument_read_write_bitop include/asm-generic/bitops/instrumented-non-atomic.h:84 [inline]
___test_and_clear_bit include/asm-generic/bitops/instrumented-non-atomic.h:114 [inline]
node_clear_mark lib/xarray.c:102 [inline]
xas_clear_mark lib/xarray.c:922 [inline]
__xa_clear_mark+0xf5/0x1e0 lib/xarray.c:2094
__folio_end_writeback+0x177/0x470 mm/page-writeback.c:3047
folio_end_writeback+0xb6/0x3a0 mm/filemap.c:1648
ext4_finish_bio+0x459/0x8c0 fs/ext4/page-io.c:144
ext4_release_io_end+0x9f/0x1f0 fs/ext4/page-io.c:159
ext4_end_io_end+0x18d/0x240 fs/ext4/page-io.c:210
ext4_do_flush_completed_IO fs/ext4/page-io.c:287 [inline]
ext4_end_io_rsv_work+0x151/0x1e0 fs/ext4/page-io.c:302
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0x4cb/0x9d0 kernel/workqueue.c:3319
worker_thread+0x582/0x770 kernel/workqueue.c:3400
kthread+0x486/0x510 kernel/kthread.c:464
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

read to 0xffff888106ce1900 of 8 bytes by task 3457 on cpu 1:
xas_find_chunk include/linux/xarray.h:1746 [inline]
xas_find_marked+0x218/0x620 lib/xarray.c:1510
find_get_entry+0x5d/0x380 mm/filemap.c:2027
filemap_get_folios_tag+0x13b/0x210 mm/filemap.c:2295
__filemap_fdatawait_range mm/filemap.c:530 [inline]
filemap_fdatawait_keep_errors+0x6c/0x180 mm/filemap.c:633
wait_sb_inodes fs/fs-writeback.c:2714 [inline]
sync_inodes_sb+0x39c/0x440 fs/fs-writeback.c:2836
sync_inodes_one_sb+0x3d/0x50 fs/sync.c:77
iterate_supers+0xa2/0x140 fs/super.c:934
ksys_sync+0x5c/0xe0 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
x64_sys_call+0x2e53/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:163
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd0/0x1a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0xfffff00000000000 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3457 Comm: syz.2.148 Not tainted 6.15.0-rc4-syzkaller-00042-gb6ea1680d0ac #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
==================================================================


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.