Hello, syzbot found the following crash on: HEAD commit: 1609d760 Merge tag 'for-linus' of git://git.kernel.org/pub.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10236abe600000 kernel config: https://syzkaller.appspot.com/x/.config?x=ed2b148cd67382ec dashboard link: https://syzkaller.appspot.com/bug?extid=ac54455281db908c581ecompiler: clang version 9.0.0 (/home/glider/llvm/clang 80fee25776c2fb61e74c1ecb1a523375c2500b69)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116c4b11600000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15ff270d600000 The bug was bisected to: commit c266f64dbfa2a970a13b0574246c0ddfec492365 Author: Vlad Buslov <vladbu@xxxxxxxxxxxx> Date: Mon Feb 11 08:55:32 2019 +0000 net: sched: protect block state with mutex bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16e7ca65600000 final crash: https://syzkaller.appspot.com/x/report.txt?x=15e7ca65600000 console output: https://syzkaller.appspot.com/x/log.txt?x=11e7ca65600000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+ac54455281db908c581e@xxxxxxxxxxxxxxxxxxxxxxxxx Fixes: c266f64dbfa2 ("net: sched: protect block state with mutex")BUG: sleeping function called from invalid context at kernel/locking/mutex.c:909
in_atomic(): 1, irqs_disabled(): 0, pid: 9297, name: syz-executor942 INFO: lockdep is turned off. Preemption disabled at: [<ffffffff8604de24>] spin_lock_bh include/linux/spinlock.h:343 [inline] [<ffffffff8604de24>] sch_tree_lock include/net/sch_generic.h:570 [inline] [<ffffffff8604de24>] sfb_change+0x284/0xd30 net/sched/sch_sfb.c:519 CPU: 0 PID: 9297 Comm: syz-executor942 Not tainted 5.3.0-rc8+ #0Hardware 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+0x1d8/0x2f8 lib/dump_stack.c:113 ___might_sleep+0x3ff/0x530 kernel/sched/core.c:6608 __might_sleep+0x8f/0x100 kernel/sched/core.c:6561 __mutex_lock_common+0x4e/0x2820 kernel/locking/mutex.c:909 __mutex_lock kernel/locking/mutex.c:1077 [inline] mutex_lock_nested+0x1b/0x30 kernel/locking/mutex.c:1092 tcf_chain0_head_change_cb_del+0x30/0x390 net/sched/cls_api.c:932 tcf_block_put_ext+0x3d/0x2a0 net/sched/cls_api.c:1502 tcf_block_put+0x6e/0x90 net/sched/cls_api.c:1515 sfb_destroy+0x47/0x70 net/sched/sch_sfb.c:467 qdisc_destroy+0x147/0x4d0 net/sched/sch_generic.c:968 qdisc_put+0x58/0x90 net/sched/sch_generic.c:992 sfb_change+0x52d/0xd30 net/sched/sch_sfb.c:522 qdisc_change net/sched/sch_api.c:1321 [inline] tc_modify_qdisc+0x184d/0x1ea0 net/sched/sch_api.c:1623 rtnetlink_rcv_msg+0x889/0xd40 net/core/rtnetlink.c:5223 netlink_rcv_skb+0x19e/0x3d0 net/netlink/af_netlink.c:2477 rtnetlink_rcv+0x1c/0x20 net/core/rtnetlink.c:5241 netlink_unicast_kernel net/netlink/af_netlink.c:1302 [inline] netlink_unicast+0x787/0x900 net/netlink/af_netlink.c:1328 netlink_sendmsg+0x993/0xc50 net/netlink/af_netlink.c:1917 sock_sendmsg_nosec net/socket.c:637 [inline] sock_sendmsg net/socket.c:657 [inline] ___sys_sendmsg+0x60d/0x910 net/socket.c:2311 __sys_sendmsg net/socket.c:2356 [inline] __do_sys_sendmsg net/socket.c:2365 [inline] __se_sys_sendmsg net/socket.c:2363 [inline] __x64_sys_sendmsg+0x17c/0x200 net/socket.c:2363 do_syscall_64+0xfe/0x140 arch/x86/entry/common.c:296 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x447509Code: e8 5c 14 03 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 ab 0e fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f49d6c94db8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00000000006dcc78 RCX: 0000000000447509 RDX: 0000000000000000 RSI: 0000000020000240 RDI: 0000000000000007 RBP: 00000000006dcc70 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00000000006dcc7c R13: 00007ffc5c2e9dff R14: 00007f49d6c959c0 R15: 000000000000002d --- 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@xxxxxxxxxxxxxxxx. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches