=============================
WARNING: suspicious RCU usage
6.3.0-rc3-syzkaller-00039-gd035230ec993 #0 Not tainted
-----------------------------
lib/maple_tree.c:856 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
6 locks held by syz-executor.6/6049:
 #0: ffff88802a73efe8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x254/0x2f0
 #1: ffff88807ec50460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x26d/0xbb0
 #2: ffff88806bde1488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1eb/0x4f0
 #3: ffff8880177fdcb8 (kn->active#49){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20f/0x4f0
 #4: ffffffff8d0107e8 (ksm_thread_mutex){+.+.}-{3:3}, at: run_store+0x122/0xb10
 #5: ffff88807af9db98 (&mm->mmap_lock){++++}-{3:3}, at: run_store+0x2db/0xb10

stack backtrace:
CPU: 0 PID: 6049 Comm: syz-executor.6 Not tainted 6.3.0-rc3-syzkaller-00039-gd035230ec993 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 dump_stack_lvl+0x1e7/0x2d0
 lockdep_rcu_suspicious+0x220/0x340
 mas_start+0x2c1/0x440
 mas_walk+0x33/0x180
 mas_find+0x1e9/0x240
 run_store+0x2f9/0xb10
 kernfs_fop_write_iter+0x3a6/0x4f0
 vfs_write+0x7b2/0xbb0
 ksys_write+0x1a0/0x2c0
 do_syscall_64+0x41/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f62e927c999
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f62ea0510c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f62e939bf80 RCX: 00007f62e927c999
RDX: 0000000000000002 RSI: 0000000020000000 RDI: 0000000000000003
RBP: 00007f62e92d8ad0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f62e939bf80 R15: 00007ffc723d21a8
 </TASK>
