From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DB2BC00140 for ; Wed, 10 Aug 2022 16:28:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232739AbiHJQ2g (ORCPT ); Wed, 10 Aug 2022 12:28:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57104 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232539AbiHJQ2f (ORCPT ); Wed, 10 Aug 2022 12:28:35 -0400 Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8FA4B82757 for ; Wed, 10 Aug 2022 09:28:33 -0700 (PDT) Received: by mail-il1-f197.google.com with SMTP id o5-20020a056e02102500b002ddcc65029cso10830814ilj.8 for ; Wed, 10 Aug 2022 09:28:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc; bh=cHi1+WEQljuM36ekuvI0X9IV++jgfJuO61bfzFoT5DA=; b=NWqvGrCRoXKWwDq7kjOqSeVxaQxskjaE8Y125tuIIwNueDJjtZ9bJ8RS9QPPom+Wb0 sqCOsYYl3Masi0oErJi9HSeUjZ0z7dGpdZJ7YQjB3g7y0KrFiVf3smtufobfUM82o9AY r17C9jpn/KVlk7J2XT+Go+WvW0cr+mzZxoGWuKKK8Otm4Z9RtLm8dfckEZTJLFf6D9b4 fUHtK0r39bv+hwLplMppgik391Xe+oBYZxT/de89N0D1BzpRfsYxtgeaQbpSiboMykgI zt3hoWpQLeaPT5hS/Th9WQeOib2K8oBtS3c08H728/n5INPw0xRkD0fORlvYlJZvqAzB 6NBQ== X-Gm-Message-State: ACgBeo2KCEbzZxn76REkro/4RWL3n2oexQ8/9hdnR2YULVj6/LQ5J4M8 UrfWhrXaqrfI+o9XACQ7PBHiN7kalxWkUUEVbL6+jTPtoPbB X-Google-Smtp-Source: AA6agR7OFUfKy2byAZlVa7eK9bU6cv1r76k73pgnJHk+wVc1veAbUYwKIj6wkdc5eoch2UgQa5uly3eI7CZjL1bdpNxqrTCHiOJT MIME-Version: 1.0 X-Received: by 2002:a05:6638:3a1a:b0:343:4ae3:9c0f with SMTP id cn26-20020a0566383a1a00b003434ae39c0fmr755814jab.271.1660148912487; Wed, 10 Aug 2022 09:28:32 -0700 (PDT) Date: Wed, 10 Aug 2022 09:28:32 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000034029905e5e58ac0@google.com> Subject: [syzbot] WARNING: suspicious RCU usage in add_v4_addrs From: syzbot To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 0966d385830d riscv: Fix auipc+jalr relocation range checks git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes console output: https://syzkaller.appspot.com/x/log.txt?x=17b4436a080000 kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921 dashboard link: https://syzkaller.appspot.com/bug?extid=27aad254a5e7479997ed compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: riscv64 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+27aad254a5e7479997ed@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ----------------------------- net/ipv6/addrconf.c:3140 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] lockdep_rcu_suspicious+0x106/0x118 kernel/locking/lockdep.c:6563 [] add_v4_addrs+0x566/0x640 net/ipv6/addrconf.c:3140 [] addrconf_gre_config net/ipv6/addrconf.c:3425 [inline] [] addrconf_notify+0x784/0x1360 net/ipv6/addrconf.c:3605 [] notifier_call_chain+0xb8/0x188 kernel/notifier.c:84 [] raw_notifier_call_chain+0x2a/0x38 kernel/notifier.c:392 [] call_netdevice_notifiers_info+0x9e/0x10c net/core/dev.c:1919 [] call_netdevice_notifiers_extack net/core/dev.c:1931 [inline] [] call_netdevice_notifiers net/core/dev.c:1945 [inline] [] __dev_notify_flags+0x108/0x1fa net/core/dev.c:8179 [] dev_change_flags+0x9c/0xba net/core/dev.c:8215 [] do_setlink+0x5d6/0x21c4 net/core/rtnetlink.c:2729 [] __rtnl_newlink+0x99e/0xfa0 net/core/rtnetlink.c:3412 [] rtnl_newlink+0x60/0x8c net/core/rtnetlink.c:3527 [] rtnetlink_rcv_msg+0x338/0x9a0 net/core/rtnetlink.c:5592 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 ============================= WARNING: suspicious RCU usage 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ----------------------------- include/linux/inetdevice.h:249 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] lockdep_rcu_suspicious+0x106/0x118 kernel/locking/lockdep.c:6563 [] __in_dev_get_rtnl include/linux/inetdevice.h:249 [inline] [] add_v4_addrs+0x394/0x640 net/ipv6/addrconf.c:3135 [] addrconf_gre_config net/ipv6/addrconf.c:3425 [inline] [] addrconf_notify+0x784/0x1360 net/ipv6/addrconf.c:3605 [] notifier_call_chain+0xb8/0x188 kernel/notifier.c:84 [] raw_notifier_call_chain+0x2a/0x38 kernel/notifier.c:392 [] call_netdevice_notifiers_info+0x9e/0x10c net/core/dev.c:1919 [] call_netdevice_notifiers_extack net/core/dev.c:1931 [inline] [] call_netdevice_notifiers net/core/dev.c:1945 [inline] [] __dev_notify_flags+0x108/0x1fa net/core/dev.c:8179 [] dev_change_flags+0x9c/0xba net/core/dev.c:8215 [] do_setlink+0x5d6/0x21c4 net/core/rtnetlink.c:2729 [] __rtnl_newlink+0x99e/0xfa0 net/core/rtnetlink.c:3412 [] rtnl_newlink+0x60/0x8c net/core/rtnetlink.c:3527 [] rtnetlink_rcv_msg+0x338/0x9a0 net/core/rtnetlink.c:5592 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 ============================= WARNING: suspicious RCU usage 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ----------------------------- net/ipv6/addrconf.c:3140 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] lockdep_rcu_suspicious+0x106/0x118 kernel/locking/lockdep.c:6563 [] add_v4_addrs+0x5e2/0x640 net/ipv6/addrconf.c:3140 [] addrconf_gre_config net/ipv6/addrconf.c:3425 [inline] [] addrconf_notify+0x784/0x1360 net/ipv6/addrconf.c:3605 [] notifier_call_chain+0xb8/0x188 kernel/notifier.c:84 [] raw_notifier_call_chain+0x2a/0x38 kernel/notifier.c:392 [] call_netdevice_notifiers_info+0x9e/0x10c net/core/dev.c:1919 [] call_netdevice_notifiers_extack net/core/dev.c:1931 [inline] [] call_netdevice_notifiers net/core/dev.c:1945 [inline] [] __dev_notify_flags+0x108/0x1fa net/core/dev.c:8179 [] dev_change_flags+0x9c/0xba net/core/dev.c:8215 [] do_setlink+0x5d6/0x21c4 net/core/rtnetlink.c:2729 [] __rtnl_newlink+0x99e/0xfa0 net/core/rtnetlink.c:3412 [] rtnl_newlink+0x60/0x8c net/core/rtnetlink.c:3527 [] rtnetlink_rcv_msg+0x338/0x9a0 net/core/rtnetlink.c:5592 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 ============================= WARNING: suspicious RCU usage 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ----------------------------- include/net/addrconf.h:313 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] lockdep_rcu_suspicious+0x106/0x118 kernel/locking/lockdep.c:6563 [] __in6_dev_get include/net/addrconf.h:313 [inline] [] __in6_dev_get include/net/addrconf.h:311 [inline] [] ipv6_mc_netdev_event+0x29c/0x4a8 net/ipv6/mcast.c:2842 [] notifier_call_chain+0xb8/0x188 kernel/notifier.c:84 [] raw_notifier_call_chain+0x2a/0x38 kernel/notifier.c:392 [] call_netdevice_notifiers_info+0x9e/0x10c net/core/dev.c:1919 [] call_netdevice_notifiers_extack net/core/dev.c:1931 [inline] [] call_netdevice_notifiers net/core/dev.c:1945 [inline] [] __dev_notify_flags+0x108/0x1fa net/core/dev.c:8179 [] dev_change_flags+0x9c/0xba net/core/dev.c:8215 [] do_setlink+0x5d6/0x21c4 net/core/rtnetlink.c:2729 [] __rtnl_newlink+0x99e/0xfa0 net/core/rtnetlink.c:3412 [] rtnl_newlink+0x60/0x8c net/core/rtnetlink.c:3527 [] rtnetlink_rcv_msg+0x338/0x9a0 net/core/rtnetlink.c:5592 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 ============================= WARNING: suspicious RCU usage 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ----------------------------- net/8021q/vlan.c:392 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] lockdep_rcu_suspicious+0x106/0x118 kernel/locking/lockdep.c:6563 [] vlan_device_event+0x364/0x1434 net/8021q/vlan.c:392 [] notifier_call_chain+0xb8/0x188 kernel/notifier.c:84 [] raw_notifier_call_chain+0x2a/0x38 kernel/notifier.c:392 [] call_netdevice_notifiers_info+0x9e/0x10c net/core/dev.c:1919 [] call_netdevice_notifiers_extack net/core/dev.c:1931 [inline] [] call_netdevice_notifiers net/core/dev.c:1945 [inline] [] __dev_notify_flags+0x108/0x1fa net/core/dev.c:8179 [] dev_change_flags+0x9c/0xba net/core/dev.c:8215 [] do_setlink+0x5d6/0x21c4 net/core/rtnetlink.c:2729 [] __rtnl_newlink+0x99e/0xfa0 net/core/rtnetlink.c:3412 [] rtnl_newlink+0x60/0x8c net/core/rtnetlink.c:3527 [] rtnetlink_rcv_msg+0x338/0x9a0 net/core/rtnetlink.c:5592 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 ===================================== WARNING: bad unlock balance detected! 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted ------------------------------------- syz-executor.1/2048 is trying to release lock (rtnl_mutex) at: [] __rtnl_unlock+0x34/0x80 net/core/rtnetlink.c:98 but there are no more locks to release! other info that might help us debug this: 1 lock held by syz-executor.1/2048: #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline] #0: 000000c00135d600 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x2fe/0x9a0 net/core/rtnetlink.c:5589 stack backtrace: CPU: 0 PID: 2048 Comm: syz-executor.1 Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] print_unlock_imbalance_bug.part.0+0xc4/0xd2 kernel/locking/lockdep.c:5080 [] print_unlock_imbalance_bug kernel/locking/lockdep.c:5062 [inline] [] __lock_release kernel/locking/lockdep.c:5316 [inline] [] lock_release+0x4fe/0x614 kernel/locking/lockdep.c:5659 [] __mutex_unlock_slowpath+0xa4/0x3a2 kernel/locking/mutex.c:893 [] mutex_unlock+0xe/0x16 kernel/locking/mutex.c:540 [] __rtnl_unlock+0x34/0x80 net/core/rtnetlink.c:98 [] netdev_run_todo+0x1ee/0x752 net/core/dev.c:9929 [] rtnl_unlock net/core/rtnetlink.c:112 [inline] [] rtnetlink_rcv_msg+0x346/0x9a0 net/core/rtnetlink.c:5593 [] netlink_rcv_skb+0xf8/0x2be net/netlink/af_netlink.c:2494 [] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:5610 [] netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline] [] netlink_unicast+0x40e/0x5fe net/netlink/af_netlink.c:1343 [] netlink_sendmsg+0x4e0/0x994 net/netlink/af_netlink.c:1919 [] sock_sendmsg_nosec net/socket.c:705 [inline] [] sock_sendmsg+0xa0/0xc4 net/socket.c:725 [] __sys_sendto+0x1f2/0x2e0 net/socket.c:2040 [] __do_sys_sendto net/socket.c:2052 [inline] [] sys_sendto+0x3e/0x52 net/socket.c:2048 [] ret_from_syscall+0x0/0x2 8021q: adding VLAN 0 to HW filter on device bond0 --- 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@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.