Hello, syzbot found the following issue on: HEAD commit: d20f6b3d747c Merge tag 'net-6.10-rc4' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1720df36980000 kernel config: https://syzkaller.appspot.com/x/.config?x=fa0ce06dcc735711 dashboard link: https://syzkaller.appspot.com/bug?extid=b62c37cdd58103293a5a 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/682e40151249/disk-d20f6b3d.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/5b5e6dd23e74/vmlinux-d20f6b3d.xz kernel image: https://storage.googleapis.com/syzbot-assets/08385974a61e/bzImage-d20f6b3d.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b62c37cdd58103293a5a@xxxxxxxxxxxxxxxxxxxxxxxxx ============================= WARNING: suspicious RCU usage 6.10.0-rc3-syzkaller-00099-gd20f6b3d747c #0 Not tainted ----------------------------- net/netfilter/ipset/ip_set_core.c:1200 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/u8:13/2892: #0: ffff888015ed5948 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline] #0: ffff888015ed5948 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312 #1: ffffc90009bcfd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline] #1: ffffc90009bcfd00 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312 #2: ffffffff8f5db250 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x16a/0xcc0 net/core/net_namespace.c:594 stack backtrace: CPU: 1 PID: 2892 Comm: kworker/u8:13 Not tainted 6.10.0-rc3-syzkaller-00099-gd20f6b3d747c #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+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 _destroy_all_sets+0x232/0x5f0 net/netfilter/ipset/ip_set_core.c:1200 ip_set_net_exit+0x20/0x50 net/netfilter/ipset/ip_set_core.c:2396 ops_exit_list net/core/net_namespace.c:173 [inline] cleanup_net+0x802/0xcc0 net/core/net_namespace.c:640 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </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 syzkaller@xxxxxxxxxxxxxxxx. 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
