syzbot


suspicious RCU usage at net/netfilter/ipset/ip_set_core.c:LINE

Status: fixed on 2018/02/01 04:00
Subsystems: netfilter
[Documentation on labels]
Reported-by: syzbot+36b06f219f2439fe62e1@syzkaller.appspotmail.com
Fix commit: f998b6b10144 netfilter: ipset: Missing nfnl_lock()/nfnl_unlock() is added to ip_set_net_exit()
First crash: 2169d, last: 2160d
Discussions (5)
Title Replies (including bot) Last reply
[PATCH 4.15 00/53] 4.15.18-stable review 58 (58) 2018/04/18 15:39
[PATCH 4.14 00/49] 4.14.35-stable review 54 (54) 2018/04/18 15:38
[PATCH 00/52] Netfilter/IPVS updates for net-next 55 (55) 2018/01/09 15:43
[PATCH 0/3] ipset patches for nf-next 5 (5) 2018/01/08 12:57
suspicious RCU usage at net/netfilter/ipset/ip_set_core.c:LINE 0 (1) 2018/01/05 10:58

Sample crash report:
=============================
WARNING: suspicious RCU usage
4.15.0-rc6-next-20180105+ #89 Not tainted
-----------------------------
net/netfilter/ipset/ip_set_core.c:2057 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/21:
 #0:  ((wq_completion)"%s""netns"){+.+.}, at: [<000000000da56a8f>] process_one_work+0x71f/0x14a0 kernel/workqueue.c:2083
 #1:  (net_cleanup_work){+.+.}, at: [<00000000b46dc045>] process_one_work+0x757/0x14a0 kernel/workqueue.c:2087
 #2:  (net_mutex){+.+.}, at: [<00000000a306ec37>] cleanup_net+0x139/0x8b0 net/core/net_namespace.c:450

stack backtrace:
CPU: 1 PID: 21 Comm: kworker/u4:1 Not tainted 4.15.0-rc6-next-20180105+ #89
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x137/0x198 lib/dump_stack.c:53
 lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4585
 ip_set_net_exit+0x2c6/0x480 net/netfilter/ipset/ip_set_core.c:2057
 ops_exit_list.isra.6+0xae/0x150 net/core/net_namespace.c:142
 cleanup_net+0x3f3/0x8b0 net/core/net_namespace.c:484
 process_one_work+0x801/0x14a0 kernel/workqueue.c:2112
 worker_thread+0xe0/0x1010 kernel/workqueue.c:2246
 kthread+0x33c/0x400 kernel/kthread.c:238
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:524

Crashes (38048):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/01/06 10:56 linux-next 990b6a07d18c 00193447 .config console log report syz C ci-upstream-next-kasan-gce
2018/01/06 10:46 mmots 69eed2290e1d 00193447 .config console log report syz C ci-upstream-mmots-kasan-gce
2018/01/02 08:42 linux-next e0e99813fb1d 00193447 .config console log report syz C ci-upstream-next-kasan-gce
2018/01/02 17:28 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:28 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:28 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:28 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:27 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:24 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:24 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:23 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:22 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:22 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:22 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:21 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:20 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:19 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:19 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:19 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:18 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:18 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:17 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:16 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:16 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:16 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:16 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:15 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:14 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:13 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:13 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:12 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:11 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:11 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:11 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:10 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:10 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:09 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:09 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:08 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:07 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:07 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:07 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
2018/01/02 17:06 linux-next e0e99813fb1d 00193447 .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.