BUG: sleeping function called from invalid context at kernel/locking/mutex.c:LINE
24 views
Skip to first unread message
syzbot
Oct 1, 2018, 2:04:03 PM10/1/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 4794a36bf08d Add linux-next specific files for 20180928
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14e16259400000
kernel config: https://syzkaller.appspot.com/x/.config?x=b0ba9bb377f8ae91
dashboard link: https://syzkaller.appspot.com/bug?extid=f81e805b090824ff5d95
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ax...@kernel.dk jo...@toxicpanda.com
linux...@vger.kernel.org linux-...@vger.kernel.org
n...@other.debian.org]
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+f81e80...@syzkaller.appspotmail.com
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
block nbd0: Connection timed out
BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:908
in_atomic(): 0, irqs_disabled(): 0, pid: 2391, name: kworker/1:1H
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8163b91c>] wake_up_klogd+0x6c/0x180 kernel/printk/printk.c:2890
CPU: 1 PID: 2391 Comm: kworker/1:1H Not tainted 4.19.0-rc5-next-20180928+
#84
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: kblockd blk_mq_timeout_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d3/0x2c4 lib/dump_stack.c:113
___might_sleep.cold.89+0x1ba/0x1f3 kernel/sched/core.c:6149
__might_sleep+0x95/0x190 kernel/sched/core.c:6102
__mutex_lock_common kernel/locking/mutex.c:908 [inline]
__mutex_lock+0x138/0x1700 kernel/locking/mutex.c:1072
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1087
sock_shutdown+0x160/0x250 drivers/block/nbd.c:335
nbd_xmit_timeout+0x2d6/0x6a0 drivers/block/nbd.c:394
blk_mq_rq_timed_out block/blk-mq.c:781 [inline]
blk_mq_check_expired+0x60e/0x740 block/blk-mq.c:841
bt_iter+0x1e5/0x260 block/blk-mq-tag.c:238
__sbitmap_for_each_set include/linux/sbitmap.h:271 [inline]
sbitmap_for_each_set include/linux/sbitmap.h:292 [inline]
bt_for_each block/blk-mq-tag.c:265 [inline]
blk_mq_queue_tag_busy_iter+0x58a/0xdb0 block/blk-mq-tag.c:405
blk_mq_timeout_work+0x34a/0x8a0 block/blk-mq.c:870
process_one_work+0xc8b/0x1b80 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
block nbd0: shutting down sockets
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
block nbd0: Attempted send on invalid socket
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
IPVS: ftp: loaded support on port[0] = 21
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered disabled state
device bridge_slave_0 entered promiscuous mode
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready
bond0: Enslaving bond_slave_0 as an active interface with an up link
bond0: Enslaving bond_slave_1 as an active interface with an up link
IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready
team0: Port device team_slave_0 added
IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready
team0: Port device team_slave_1 added
IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered forwarding state
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered forwarding state
8021q: adding VLAN 0 to HW filter on device bond0
IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
block nbd0: Attempted send on invalid socket
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
block nbd0: NBD_DISCONNECT
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 0 PID: 825 Comm: syz-executor3 Tainted: G W
4.19.0-rc5-next-20180928+ #84
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+0x1d3/0x2c4 lib/dump_stack.c:113
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold.4+0xa/0x17 lib/fault-inject.c:149
__should_failslab+0x124/0x180 mm/failslab.c:32
should_failslab+0x9/0x14 mm/slab_common.c:1578
slab_pre_alloc_hook mm/slab.h:423 [inline]
slab_alloc_node mm/slab.c:3299 [inline]
kmem_cache_alloc_node+0x26e/0x730 mm/slab.c:3642
__alloc_skb+0x114/0x770 net/core/skbuff.c:193
alloc_skb include/linux/skbuff.h:997 [inline]
netlink_alloc_large_skb net/netlink/af_netlink.c:1182 [inline]
netlink_sendmsg+0xb29/0xfc0 net/netlink/af_netlink.c:1876
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xd5/0x120 net/socket.c:632
sock_xmit.isra.14+0x2cc/0x700 drivers/block/nbd.c:432
send_disconnects drivers/block/nbd.c:1078 [inline]
nbd_disconnect+0x3e1/0x570 drivers/block/nbd.c:1092
__nbd_ioctl drivers/block/nbd.c:1235 [inline]
nbd_ioctl+0x3c6/0xd40 drivers/block/nbd.c:1306
__blkdev_driver_ioctl block/ioctl.c:303 [inline]
blkdev_ioctl+0x9ac/0x2010 block/ioctl.c:601
block_ioctl+0xee/0x130 fs/block_dev.c:1883
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457579
Code: 1d b4 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 eb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7690bd6c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7690bd6c90 RCX: 0000000000457579
RDX: 0000000000000000 RSI: 000000000000ab08 RDI: 0000000000000004
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7690bd76d4
R13: 00000000004c04d6 R14: 00000000004d0678 R15: 0000000000000005
block nbd0: Send disconnect failed -105
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
team0 (unregistering): Port device team_slave_1 removed
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot found the following crash on:
HEAD commit: 4794a36bf08d Add linux-next specific files for 20180928
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14e16259400000
kernel config: https://syzkaller.appspot.com/x/.config?x=b0ba9bb377f8ae91
dashboard link: https://syzkaller.appspot.com/bug?extid=f81e805b090824ff5d95
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ax...@kernel.dk jo...@toxicpanda.com
linux...@vger.kernel.org linux-...@vger.kernel.org
n...@other.debian.org]
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+f81e80...@syzkaller.appspotmail.com
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
block nbd0: Connection timed out
BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:908
in_atomic(): 0, irqs_disabled(): 0, pid: 2391, name: kworker/1:1H
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8163b91c>] wake_up_klogd+0x6c/0x180 kernel/printk/printk.c:2890
CPU: 1 PID: 2391 Comm: kworker/1:1H Not tainted 4.19.0-rc5-next-20180928+
#84
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: kblockd blk_mq_timeout_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d3/0x2c4 lib/dump_stack.c:113
___might_sleep.cold.89+0x1ba/0x1f3 kernel/sched/core.c:6149
__might_sleep+0x95/0x190 kernel/sched/core.c:6102
__mutex_lock_common kernel/locking/mutex.c:908 [inline]
__mutex_lock+0x138/0x1700 kernel/locking/mutex.c:1072
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1087
sock_shutdown+0x160/0x250 drivers/block/nbd.c:335
nbd_xmit_timeout+0x2d6/0x6a0 drivers/block/nbd.c:394
blk_mq_rq_timed_out block/blk-mq.c:781 [inline]
blk_mq_check_expired+0x60e/0x740 block/blk-mq.c:841
bt_iter+0x1e5/0x260 block/blk-mq-tag.c:238
__sbitmap_for_each_set include/linux/sbitmap.h:271 [inline]
sbitmap_for_each_set include/linux/sbitmap.h:292 [inline]
bt_for_each block/blk-mq-tag.c:265 [inline]
blk_mq_queue_tag_busy_iter+0x58a/0xdb0 block/blk-mq-tag.c:405
blk_mq_timeout_work+0x34a/0x8a0 block/blk-mq.c:870
process_one_work+0xc8b/0x1b80 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
block nbd0: shutting down sockets
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
block nbd0: Attempted send on invalid socket
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
IPVS: ftp: loaded support on port[0] = 21
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered disabled state
device bridge_slave_0 entered promiscuous mode
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready
bond0: Enslaving bond_slave_0 as an active interface with an up link
bond0: Enslaving bond_slave_1 as an active interface with an up link
IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready
team0: Port device team_slave_0 added
IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready
team0: Port device team_slave_1 added
IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered forwarding state
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered forwarding state
8021q: adding VLAN 0 to HW filter on device bond0
IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
block nbd0: Attempted send on invalid socket
print_req_error: I/O error, dev nbd0, sector 0
XFS (nbd0): SB validate failed with error -5.
block nbd0: NBD_DISCONNECT
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 0 PID: 825 Comm: syz-executor3 Tainted: G W
4.19.0-rc5-next-20180928+ #84
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+0x1d3/0x2c4 lib/dump_stack.c:113
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold.4+0xa/0x17 lib/fault-inject.c:149
__should_failslab+0x124/0x180 mm/failslab.c:32
should_failslab+0x9/0x14 mm/slab_common.c:1578
slab_pre_alloc_hook mm/slab.h:423 [inline]
slab_alloc_node mm/slab.c:3299 [inline]
kmem_cache_alloc_node+0x26e/0x730 mm/slab.c:3642
__alloc_skb+0x114/0x770 net/core/skbuff.c:193
alloc_skb include/linux/skbuff.h:997 [inline]
netlink_alloc_large_skb net/netlink/af_netlink.c:1182 [inline]
netlink_sendmsg+0xb29/0xfc0 net/netlink/af_netlink.c:1876
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xd5/0x120 net/socket.c:632
sock_xmit.isra.14+0x2cc/0x700 drivers/block/nbd.c:432
send_disconnects drivers/block/nbd.c:1078 [inline]
nbd_disconnect+0x3e1/0x570 drivers/block/nbd.c:1092
__nbd_ioctl drivers/block/nbd.c:1235 [inline]
nbd_ioctl+0x3c6/0xd40 drivers/block/nbd.c:1306
__blkdev_driver_ioctl block/ioctl.c:303 [inline]
blkdev_ioctl+0x9ac/0x2010 block/ioctl.c:601
block_ioctl+0xee/0x130 fs/block_dev.c:1883
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457579
Code: 1d b4 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 eb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7690bd6c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7690bd6c90 RCX: 0000000000457579
RDX: 0000000000000000 RSI: 000000000000ab08 RDI: 0000000000000004
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7690bd76d4
R13: 00000000004c04d6 R14: 00000000004d0678 R15: 0000000000000005
block nbd0: Send disconnect failed -105
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
team0 (unregistering): Port device team_slave_1 removed
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
Dmitry Vyukov
May 7, 2019, 5:25:46 AM5/7/19
to syzbot, Andrey Konovalov, 'Dmitry Vyukov' via syzkaller-upstream-moderation
This will now be detected with a different title (after
148296f4787895d1b148d29a2f48140bcfd245a3). So close this.
#syz invalid
> Hardware name: Google Google Compute EBUG: sleeping function called from invalid context at kernel/locking/mutex.c:LINEngine/Google Compute Engine, BIOS
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000005812d205772ea130%40google.com.
> For more options, visit https://groups.google.com/d/optout.
148296f4787895d1b148d29a2f48140bcfd245a3). So close this.
#syz invalid
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000005812d205772ea130%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages