=============================
WARNING: suspicious RCU usage
6.2.0-rc7-syzkaller-17891-geaed33698e35 #0 Not tainted
-----------------------------
lib/maple_tree.c:852 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.5/10514:
 #0: ffff0000ca43f6e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x12c/0x154
 #1: ffff0000c8d14460 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x174/0x44c
 #2: ffff0000c967ba88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x120/0x288
 #3: ffff0000c039f4a0 (kn->active#57){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x128/0x288
 #4: ffff80000d4bc640 (ksm_thread_mutex){+.+.}-{3:3}, at: run_store+0x8c/0x608
 #5: ffff0000c1fb5248 (&mm->mmap_lock){++++}-{3:3}, at: run_store+0x200/0x608

stack backtrace:
CPU: 1 PID: 10514 Comm: syz-executor.5 Not tainted 6.2.0-rc7-syzkaller-17891-geaed33698e35 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call trace:
 dump_backtrace+0x1c8/0x1f4
 show_stack+0x2c/0x3c
 dump_stack_lvl+0xd0/0x124
 dump_stack+0x1c/0x28
 lockdep_rcu_suspicious+0x138/0x154
 mas_state_walk+0x1a4/0x200
 mas_walk+0x2c/0xc4
 mas_find+0x10c/0x13c
 run_store+0x214/0x608
 kobj_attr_store+0x4c/0x70
 sysfs_kf_write+0xf4/0x11c
 kernfs_fop_write_iter+0x1d8/0x288
 vfs_write+0x2bc/0x44c
 ksys_write+0xb4/0x160
 __arm64_sys_write+0x24/0x34
 invoke_syscall+0x64/0x178
 el0_svc_common+0xbc/0x180
 do_el0_svc+0x48/0x110
 el0_svc+0x58/0x14c
 el0t_64_sync_handler+0x84/0xf0
 el0t_64_sync+0x190/0x194