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 X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 72C9EC4741F for ; Tue, 10 Nov 2020 18:25:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 30FC7206B6 for ; Tue, 10 Nov 2020 18:25:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731359AbgKJSZV (ORCPT ); Tue, 10 Nov 2020 13:25:21 -0500 Received: from mail-io1-f70.google.com ([209.85.166.70]:54582 "EHLO mail-io1-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731259AbgKJSZT (ORCPT ); Tue, 10 Nov 2020 13:25:19 -0500 Received: by mail-io1-f70.google.com with SMTP id h11so1931731iob.21 for ; Tue, 10 Nov 2020 10:25:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=5k/KfaC6hpzMbrmO2ub4fMk/eikFub437ScdVpWXUuE=; b=ssRIkaQacmTK1BNwrHK0k4gGv5WAAnOpRYJI34peQ7Zd2TTmXU2xw0vb1W6lkwy6uW COimwoxRp9bm6xCN9l0GAweTd3mC1UVCP2SHaACPiMi+36dl3e4YaFSd703G6SOH9WSi /MO6aiX4EkpqzeWZ4qjA4m8vCJQOC0DLf1u70ehqf+AomfED1lhqrl0EKt+8nI/xaXJr E/uE/CU2VpI9+ORN2VfuC7M6Y1aFeptWq/1MHJPRi83fA0R4W1clH4lVWzNF21VAqPLE 6OoBCps7lM90beC6SefhL/Czg37+e2eqOC+za2VlWcW/YZLwZqzhJ5/qBFwXduj7pQkY kq9w== X-Gm-Message-State: AOAM533NT+OH/mJcuBGomMPNX6Jt7uvm6/45Qk2LlLEjuubJQw3jvmkq qwT11ORkJQVej8Sd67UHFRNjwMWVCamJqRADgKCy7d2HvJnU X-Google-Smtp-Source: ABdhPJz2y+PtpZTBKc5pN2jHseHQMxUuJwAUGNtfRmS7Gv+OFb6IQqO9jNUUQoe/7L7psLd2KD4vcS8GfQ5BejuBRIqYIrRYPyv3 MIME-Version: 1.0 X-Received: by 2002:a92:5b46:: with SMTP id p67mr15069330ilb.150.1605032718305; Tue, 10 Nov 2020 10:25:18 -0800 (PST) Date: Tue, 10 Nov 2020 10:25:18 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000007105605b3c4cdbf@google.com> Subject: net-next test error: BUG: sleeping function called from invalid context in sta_info_move_state From: syzbot To: davem@davemloft.net, johannes@sipsolutions.net, kuba@kernel.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: a3ce2b10 net: udp: introduce UDP_MIB_MEMERRORS for udp_mem git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=12a0df46500000 kernel config: https://syzkaller.appspot.com/x/.config?x=7891ad1ca1723c54 dashboard link: https://syzkaller.appspot.com/bug?extid=4c81fe92e372d26c4246 compiler: gcc (GCC) 10.1.0-syz 20200507 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+4c81fe92e372d26c4246@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at net/mac80211/sta_info.c:1962 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 21, name: kworker/u4:1 4 locks held by kworker/u4:1/21: #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: process_one_work+0x821/0x15a0 kernel/workqueue.c:2243 #1: ffffc90000dbfda8 ((work_completion)(&sdata->work)){+.+.}-{0:0}, at: process_one_work+0x854/0x15a0 kernel/workqueue.c:2247 #2: ffff8880355c8d00 (&wdev->mtx){+.+.}-{3:3}, at: sdata_lock net/mac80211/ieee80211_i.h:1021 [inline] #2: ffff8880355c8d00 (&wdev->mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0x93/0xe80 net/mac80211/ibss.c:1683 #3: ffffffff8b337160 (rcu_read_lock){....}-{1:2}, at: sta_info_insert_finish net/mac80211/sta_info.c:644 [inline] #3: ffffffff8b337160 (rcu_read_lock){....}-{1:2}, at: sta_info_insert_rcu+0x680/0x2ba0 net/mac80211/sta_info.c:732 Preemption disabled at: [] __mutex_lock_common kernel/locking/mutex.c:955 [inline] [] __mutex_lock+0x10f/0x10e0 kernel/locking/mutex.c:1103 CPU: 1 PID: 21 Comm: kworker/u4:1 Not tainted 5.10.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: phy3 ieee80211_iface_work Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:118 ___might_sleep.cold+0x1e8/0x22e kernel/sched/core.c:7298 sta_info_move_state+0x32/0x8d0 net/mac80211/sta_info.c:1962 sta_info_free+0x65/0x3b0 net/mac80211/sta_info.c:274 sta_info_insert_rcu+0x303/0x2ba0 net/mac80211/sta_info.c:738 ieee80211_ibss_finish_sta+0x212/0x390 net/mac80211/ibss.c:592 ieee80211_ibss_work+0x2c7/0xe80 net/mac80211/ibss.c:1700 ieee80211_iface_work+0x91f/0xa90 net/mac80211/iface.c:1478 process_one_work+0x933/0x15a0 kernel/workqueue.c:2272 worker_thread+0x64c/0x1120 kernel/workqueue.c:2418 kthread+0x3af/0x4a0 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296 ============================= [ BUG: Invalid wait context ] 5.10.0-rc2-syzkaller #0 Tainted: G W ----------------------------- kworker/u4:1/21 is trying to lock: ffff88802d8729d0 (&local->chanctx_mtx){+.+.}-{3:3}, at: ieee80211_recalc_min_chandef+0x49/0x140 net/mac80211/util.c:2741 other info that might help us debug this: context-{4:4} 4 locks held by kworker/u4:1/21: #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline] #0: ffff8880247dc138 ((wq_completion)phy3){+.+.}-{0:0}, at: process_one_work+0x821/0x15a0 kernel/workqueue.c:2243 #1: ffffc90000dbfda8 ((work_completion)(&sdata->work)){+.+.}-{0:0}, at: process_one_work+0x854/0x15a0 kernel/workqueue.c:2247 #2: ffff8880355c8d00 (&wdev->mtx){+.+.}-{3:3}, at: sdata_lock net/mac80211/ieee80211_i.h:1021 [inline] #2: ffff8880355c8d00 (&wdev->mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0x93/0xe80 net/mac80211/ibss.c:1683 #3: ffffffff8b337160 (rcu_read_lock){....}-{1:2}, at: sta_info_insert_finish net/mac80211/sta_info.c:644 [inline] #3: ffffffff8b337160 (rcu_read_lock){....}-{1:2}, at: sta_info_insert_rcu+0x680/0x2ba0 net/mac80211/sta_info.c:732 stack backtrace: CPU: 1 PID: 21 Comm: kworker/u4:1 Tainted: G W 5.10.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: phy3 ieee80211_iface_work Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:118 print_lock_invalid_wait_context kernel/locking/lockdep.c:4483 [inline] check_wait_context kernel/locking/lockdep.c:4544 [inline] __lock_acquire.cold+0x310/0x3a2 kernel/locking/lockdep.c:4781 lock_acquire kernel/locking/lockdep.c:5436 [inline] lock_acquire+0x2a3/0x8c0 kernel/locking/lockdep.c:5401 __mutex_lock_common kernel/locking/mutex.c:956 [inline] __mutex_lock+0x134/0x10e0 kernel/locking/mutex.c:1103 ieee80211_recalc_min_chandef+0x49/0x140 net/mac80211/util.c:2741 sta_info_move_state+0x3cf/0x8d0 net/mac80211/sta_info.c:2019 sta_info_free+0x65/0x3b0 net/mac80211/sta_info.c:274 sta_info_insert_rcu+0x303/0x2ba0 net/mac80211/sta_info.c:738 ieee80211_ibss_finish_sta+0x212/0x390 net/mac80211/ibss.c:592 ieee80211_ibss_work+0x2c7/0xe80 net/mac80211/ibss.c:1700 ieee80211_iface_work+0x91f/0xa90 net/mac80211/iface.c:1478 process_one_work+0x933/0x15a0 kernel/workqueue.c:2272 worker_thread+0x64c/0x1120 kernel/workqueue.c:2418 kthread+0x3af/0x4a0 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296 netdevsim netdevsim0 netdevsim3 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim2 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim1 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim0 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0 device hsr_slave_0 left promiscuous mode device hsr_slave_1 left promiscuous mode batman_adv: batadv0: Interface deactivated: batadv_slave_0 batman_adv: batadv0: Removing interface: batadv_slave_0 batman_adv: batadv0: Interface deactivated: batadv_slave_1 batman_adv: batadv0: Removing interface: batadv_slave_1 device bridge_slave_1 left promiscuous mode bridge0: port 2(bridge_slave_1) entered disabled state device bridge_slave_0 left promiscuous mode bridge0: port 1(bridge_slave_0) entered disabled state device veth1_macvtap left promiscuous mode device veth0_macvtap left promiscuous mode device veth1_vlan left promiscuous mode device veth0_vlan left promiscuous mode team0 (unregistering): Port device team_slave_1 removed team0 (unregistering): Port device team_slave_0 removed bond0 (unregistering): (slave bond_slave_1): Releasing backup interface bond0 (unregistering): (slave bond_slave_0): Releasing backup interface bond0 (unregistering): Released all slaves --- 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.