WARNING: suspicious RCU usage in vzalloc

8 views
Skip to first unread message

syzbot

unread,
Jul 22, 2020, 10:11:21 PM7/22/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 69b94dd6 Linux 4.14.189
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d94640900000
kernel config: https://syzkaller.appspot.com/x/.config?x=80d63ff414fa81b0
dashboard link: https://syzkaller.appspot.com/bug?extid=53abf71dd094129cbc54
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

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

=============================
syz-executor.4: vmalloc: allocation failure: 17179869200 bytes, mode:0x14080c0(GFP_KERNEL|__GFP_ZERO), nodemask=(null)
WARNING: suspicious RCU usage
4.14.189-syzkaller #0 Not tainted
-----------------------------
net/tipc/bearer.c:177 suspicious rcu_dereference_protected() usage!

other info that might help us debug this:

syz-executor.4 cpuset=/ mems_allowed=0-1

rcu_scheduler_active = 2, debug_locks = 1
CPU: 1 PID: 19226 Comm: syz-executor.4 Not tainted 4.14.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
warn_alloc.cold+0x96/0x1cc mm/page_alloc.c:3249
2 locks held by syz-executor.2/19223:
__vmalloc_node_range mm/vmalloc.c:1789 [inline]
__vmalloc_node mm/vmalloc.c:1818 [inline]
__vmalloc_node_flags mm/vmalloc.c:1832 [inline]
vzalloc+0x122/0x150 mm/vmalloc.c:1871
ip_set_alloc+0x47/0x60 net/netfilter/ipset/ip_set_core.c:261
hash_ip_create+0x43e/0xb80 net/netfilter/ipset/ip_set_hash_gen.h:1303
ip_set_create+0x5f9/0xf30 net/netfilter/ipset/ip_set_core.c:911
#0:
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
(
cb_lock
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
){++++}
, at: [<ffffffff85302c25>] genl_rcv+0x15/0x40 net/netlink/genetlink.c:635
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
#1:
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
(
RIP: 0033:0x45c1f9
RSP: 002b:00007f7ae4f81c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000027d00 RCX: 000000000045c1f9
RDX: 0000000000000000 RSI: 0000000020001080 RDI: 0000000000000003
RBP: 000000000078bf40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000078bf0c
R13: 00007ffe0900d47f R14: 00007f7ae4f829c0 R15: 000000000078bf0c
genl_mutex){+.+.}, at: [<ffffffff85303882>] genl_lock net/netlink/genetlink.c:33 [inline]
genl_mutex){+.+.}, at: [<ffffffff85303882>] genl_rcv_msg+0x112/0x140 net/netlink/genetlink.c:623

stack backtrace:
CPU: 0 PID: 19223 Comm: syz-executor.2 Not tainted 4.14.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
tipc_bearer_find+0x1ff/0x2f0 net/tipc/bearer.c:177
tipc_nl_compat_link_set+0x40b/0xb90 net/tipc/netlink_compat.c:797
__tipc_nl_compat_doit net/tipc/netlink_compat.c:306 [inline]
tipc_nl_compat_doit+0x192/0x5d0 net/tipc/netlink_compat.c:354
tipc_nl_compat_handle net/tipc/netlink_compat.c:1205 [inline]
tipc_nl_compat_recv+0xa0b/0xae0 net/tipc/netlink_compat.c:1287
genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600
genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
genl_rcv+0x24/0x40 net/netlink/genetlink.c:636
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45c1f9
RSP: 002b:00007fa6d8985c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002a940 RCX: 000000000045c1f9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000003
RBP: 000000000078bf40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000078bf0c
R13: 00007ffd349b4e8f R14: 00007fa6d89869c0 R15: 000000000078bf0c
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready
NOHZ: local_softirq_pending 08
IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready


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

syzbot

unread,
Nov 19, 2020, 9:11:11 PM11/19/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages