From: Dmitry Vyukov <dvyukov@google.com> To: syzbot <syzbot+692f39f040c1f415567b@syzkaller.appspotmail.com>, syzkaller-bugs <syzkaller-bugs@googlegroups.com>, LKML <linux-kernel@vger.kernel.org> Subject: Re: BUG: MAX_LOCKDEP_KEYS too low! Date: Wed, 9 Dec 2020 09:01:28 +0100 [thread overview] Message-ID: <CACT4Y+avvqLabSr+4GL-GSah5YMxvM+u2_yTcjT=xtA14YXS_w@mail.gmail.com> (raw) In-Reply-To: <0000000000009ea5720595dc03a3@google.com> On Sun, Oct 27, 2019 at 4:31 AM syzbot <syzbot+692f39f040c1f415567b@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: 65921376 Merge branch 'net-fix-nested-device-bugs' > git tree: net > console output: https://syzkaller.appspot.com/x/log.txt?x=1637fdc0e00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=e0ac4d9b35046343 > dashboard link: https://syzkaller.appspot.com/bug?extid=692f39f040c1f415567b > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > Unfortunately, I don't have any reproducer for this crash yet. > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+692f39f040c1f415567b@syzkaller.appspotmail.com This stopped happening a while ago, let's close this to get notifications about new instances. One of likely candidates: #syz fix: net: partially revert dynamic lockdep key changes > BUG: MAX_LOCKDEP_KEYS too low! > turning off the locking correctness validator. > CPU: 0 PID: 15175 Comm: syz-executor.5 Not tainted 5.4.0-rc3+ #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:77 [inline] > dump_stack+0x172/0x1f0 lib/dump_stack.c:113 > register_lock_class.cold+0x1b/0x27 kernel/locking/lockdep.c:1222 > __lock_acquire+0xf4/0x4a00 kernel/locking/lockdep.c:3837 > lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4487 > __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline] > _raw_spin_lock_bh+0x33/0x50 kernel/locking/spinlock.c:175 > spin_lock_bh include/linux/spinlock.h:343 [inline] > netif_addr_lock_bh include/linux/netdevice.h:4055 [inline] > __dev_mc_add+0x2e/0xd0 net/core/dev_addr_lists.c:765 > dev_mc_add+0x20/0x30 net/core/dev_addr_lists.c:783 > igmp6_group_added+0x3b5/0x460 net/ipv6/mcast.c:672 > __ipv6_dev_mc_inc+0x727/0xa60 net/ipv6/mcast.c:931 > ipv6_dev_mc_inc+0x20/0x30 net/ipv6/mcast.c:938 > ipv6_add_dev net/ipv6/addrconf.c:456 [inline] > ipv6_add_dev+0xa3d/0x10b0 net/ipv6/addrconf.c:363 > addrconf_notify+0x97d/0x23b0 net/ipv6/addrconf.c:3491 > notifier_call_chain+0xc2/0x230 kernel/notifier.c:95 > __raw_notifier_call_chain kernel/notifier.c:396 [inline] > raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:403 > call_netdevice_notifiers_info+0x3f/0x90 net/core/dev.c:1668 > call_netdevice_notifiers_extack net/core/dev.c:1680 [inline] > call_netdevice_notifiers net/core/dev.c:1694 [inline] > register_netdevice+0x950/0xeb0 net/core/dev.c:9114 > ieee80211_if_add+0xf51/0x1730 net/mac80211/iface.c:1881 > ieee80211_register_hw+0x36e6/0x3ac0 net/mac80211/main.c:1256 > mac80211_hwsim_new_radio+0x20d9/0x4360 > drivers/net/wireless/mac80211_hwsim.c:3031 > hwsim_new_radio_nl+0x9e3/0x1070 drivers/net/wireless/mac80211_hwsim.c:3586 > genl_family_rcv_msg+0x74b/0xf90 net/netlink/genetlink.c:629 > genl_rcv_msg+0xca/0x170 net/netlink/genetlink.c:654 > netlink_rcv_skb+0x177/0x450 net/netlink/af_netlink.c:2477 > genl_rcv+0x29/0x40 net/netlink/genetlink.c:665 > netlink_unicast_kernel net/netlink/af_netlink.c:1302 [inline] > netlink_unicast+0x531/0x710 net/netlink/af_netlink.c:1328 > netlink_sendmsg+0x8a5/0xd60 net/netlink/af_netlink.c:1917 > sock_sendmsg_nosec net/socket.c:637 [inline] > sock_sendmsg+0xd7/0x130 net/socket.c:657 > ___sys_sendmsg+0x803/0x920 net/socket.c:2311 > __sys_sendmsg+0x105/0x1d0 net/socket.c:2356 > __do_sys_sendmsg net/socket.c:2365 [inline] > __se_sys_sendmsg net/socket.c:2363 [inline] > __x64_sys_sendmsg+0x78/0xb0 net/socket.c:2363 > do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290 > entry_SYSCALL_64_after_hwframe+0x49/0xbe > RIP: 0033:0x459f39 > Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 > 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff > ff 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 > RSP: 002b:00007fd0af43ac78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e > RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459f39 > RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000003 > RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000 > R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd0af43b6d4 > R13: 00000000004c82f8 R14: 00000000004de3f0 R15: 00000000ffffffff > kobject: 'batman_adv' (000000009392522f): kobject_add_internal: > parent: 'wlan1810', set: '<NULL>' > > > --- > This bug 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 bug report. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/0000000000009ea5720595dc03a3%40google.com.
next prev parent reply other threads:[~2020-12-09 8:09 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-27 3:31 syzbot 2019-10-29 2:13 ` syzbot 2019-10-29 14:09 ` syzbot 2019-10-29 14:09 ` syzbot 2019-11-01 15:08 ` syzbot 2019-11-01 15:08 ` syzbot 2020-12-09 8:01 ` Dmitry Vyukov [this message] 2021-01-22 3:43 Alexey Kardashevskiy 2021-01-22 9:16 ` Dmitry Vyukov [not found] ` <6af41136-4344-73da-f821-e831674be473@i-love.sakura.ne.jp> [not found] ` <70d427e8-7281-0aae-c524-813d73eca2d7@ozlabs.ru> [not found] ` <CACT4Y+bqidtwh1HUFFoyyKyVy0jnwrzhVBgqmU+T9sN1yPMO=g@mail.gmail.com> [not found] ` <eb71cc37-afbd-5446-6305-8c7abcc6e91f@i-love.sakura.ne.jp> [not found] ` <6eaafbd8-1c10-75df-75ae-9afa0861f69b@i-love.sakura.ne.jp> 2021-01-22 22:53 ` Alexey Kardashevskiy [not found] ` <20210123060145.18356-1-hdanton@sina.com> 2021-01-23 6:35 ` Alexey Kardashevskiy 2021-01-23 10:29 ` Tetsuo Handa 2021-01-23 11:26 ` Alexey Kardashevskiy 2021-01-23 13:12 ` Tetsuo Handa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACT4Y+avvqLabSr+4GL-GSah5YMxvM+u2_yTcjT=xtA14YXS_w@mail.gmail.com' \ --to=dvyukov@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=syzbot+692f39f040c1f415567b@syzkaller.appspotmail.com \ --cc=syzkaller-bugs@googlegroups.com \ --subject='Re: BUG: MAX_LOCKDEP_KEYS too low'\!'' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.