[v6.1] linux-6.1.y test error: WARNING: suspicious RCU usage in _destroy_all_sets

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a6398e373090 Linux 6.1.95
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1611c201980000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd7de5aefd963cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=6ff52cdac2ce99b7444a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0847ecbd05f4/disk-a6398e37.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bcdf6685168c/vmlinux-a6398e37.xz
kernel image: https://storage.googleapis.com/syzbot-assets/36296f088c67/bzImage-a6398e37.xz

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

=============================
WARNING: suspicious RCU usage
6.1.95-syzkaller #0 Not tainted
-----------------------------
net/netfilter/ipset/ip_set_core.c:1202 suspicious rcu_dereference_protected() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u4:1/11:
#0: ffff888012616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90000107d20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8e28d9d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:566

stack backtrace:
CPU: 1 PID: 11 Comm: kworker/u4:1 Not tainted 6.1.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: netns cleanup_net
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
lockdep_rcu_suspicious+0x21c/0x330 kernel/locking/lockdep.c:6592
_destroy_all_sets+0x22c/0x5e0 net/netfilter/ipset/ip_set_core.c:1202
ip_set_net_exit+0x1c/0x50 net/netfilter/ipset/ip_set_core.c:2398
ops_exit_list net/core/net_namespace.c:172 [inline]
cleanup_net+0x6ce/0xb60 net/core/net_namespace.c:604
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>

=============================
WARNING: suspicious RCU usage
6.1.95-syzkaller #0 Not tainted
-----------------------------
net/netfilter/ipset/ip_set_core.c:1213 suspicious rcu_dereference_protected() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u4:1/11:
#0: ffff888012616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90000107d20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8e28d9d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:566

stack backtrace:
CPU: 1 PID: 11 Comm: kworker/u4:1 Not tainted 6.1.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: netns cleanup_net
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
lockdep_rcu_suspicious+0x21c/0x330 kernel/locking/lockdep.c:6592
_destroy_all_sets+0x533/0x5e0 net/netfilter/ipset/ip_set_core.c:1213
ip_set_net_exit+0x1c/0x50 net/netfilter/ipset/ip_set_core.c:2398
ops_exit_list net/core/net_namespace.c:172 [inline]
cleanup_net+0x6ce/0xb60 net/core/net_namespace.c:604
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>


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