possible deadlock in team_vlan_rx_add_vid
9 views
Skip to first unread message
syzbot
Aug 31, 2020, 9:47:15 PM8/31/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1407a279900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=f6d6eb54399925b08415
compiler: gcc (GCC) 10.1.0-syz 20200507
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+f6d6eb...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
4.14.195-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.0/7679 is trying to acquire lock:
(&team->lock){+.+.}, at: [<ffffffff83e460b8>] team_vlan_rx_add_vid+0x38/0x1d0 drivers/net/team/team.c:1889
but task is already holding lock:
(&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by syz-executor.0/7679:
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnetlink_rcv_msg+0x31d/0xb10 net/core/rtnetlink.c:4311
#1: (&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
stack backtrace:
CPU: 0 PID: 7679 Comm: syz-executor.0 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_deadlock_bug kernel/locking/lockdep.c:1800 [inline]
check_deadlock kernel/locking/lockdep.c:1847 [inline]
validate_chain kernel/locking/lockdep.c:2448 [inline]
__lock_acquire.cold+0x180/0x97c kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
team_vlan_rx_add_vid+0x38/0x1d0 drivers/net/team/team.c:1889
__vlan_vid_add net/8021q/vlan_core.c:219 [inline]
vlan_vid_add+0x5ef/0x7d0 net/8021q/vlan_core.c:251
__vlan_vid_add net/8021q/vlan_core.c:219 [inline]
vlan_vid_add+0x5ef/0x7d0 net/8021q/vlan_core.c:251
vlan_device_event.cold+0x23/0x28 net/8021q/vlan.c:372
notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93
call_netdevice_notifiers_info net/core/dev.c:1667 [inline]
call_netdevice_notifiers net/core/dev.c:1683 [inline]
dev_open net/core/dev.c:1407 [inline]
dev_open+0xf9/0x110 net/core/dev.c:1395
team_port_add drivers/net/team/team.c:1214 [inline]
team_add_slave+0x954/0x1ad0 drivers/net/team/team.c:1968
do_set_master+0x19e/0x200 net/core/rtnetlink.c:1961
rtnl_newlink+0x134c/0x1830 net/core/rtnetlink.c:2757
rtnetlink_rcv_msg+0x3be/0xb10 net/core/rtnetlink.c:4316
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45d5b9
RSP: 002b:00007f02dd5d6c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002ce80 RCX: 000000000045d5b9
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffd3d2a361f R14: 00007f02dd5d79c0 R15: 000000000118cf4c
team0: Device macvtap1 failed to register rx_handler
audit: type=1804 audit(1598924767.179:493): pid=7692 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
audit: type=1804 audit(1598924767.409:494): pid=7710 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir610673552/syzkaller.i9eLlq/156/file0" dev="sda1" ino=16457 res=1
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
team0: Device macvtap1 failed to register rx_handler
audit: type=1804 audit(1598924767.419:495): pid=7710 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir610673552/syzkaller.i9eLlq/156/file0" dev="sda1" ino=16457 res=1
audit: type=1804 audit(1598924767.639:496): pid=7692 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
audit: type=1804 audit(1598924767.639:497): pid=7732 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
8021q: adding VLAN 0 to HW filter on device macvtap1
team0: Device macvtap1 failed to register rx_handler
REISERFS warning (device loop3): super-6508 reiserfs_parse_options: bad value 0x0000000000000000= for -ocommit
IPVS: ftp: loaded support on port[0] = 21
BFS-fs: bfs_fill_super(): Inode 0x00000026 corrupted
BFS-fs: bfs_fill_super(): Inode 0x00000026 corrupted
attempt to access beyond end of device
loop5: rw=1, want=230, limit=127
ip6_tables: ip6tables: counters copy to user failed while replacing table
new mount options do not match the existing superblock, will be ignored
hfs: dir_umask requires a value
ip6_tables: ip6tables: counters copy to user failed while replacing table
hfs: unable to parse mount options
new mount options do not match the existing superblock, will be ignored
ip6_tables: ip6tables: counters copy to user failed while replacing table
audit: type=1804 audit(1598924769.559:498): pid=7918 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir179861148/syzkaller.xjkBIl/269/bus" dev="sda1" ino=16471 res=1
ip6_tables: ip6tables: counters copy to user failed while replacing table
audit: type=1804 audit(1598924769.559:499): pid=7917 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir179861148/syzkaller.xjkBIl/269/bus" dev="sda1" ino=16471 res=1
audit: type=1800 audit(1598924769.609:500): pid=7866 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=16464 res=0
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
IPVS: ftp: loaded support on port[0] = 21
IPVS: length: 209 != 8
9pnet: Insufficient options for proto=fd
overlayfs: filesystem on './file0' not supported as upperdir
audit: type=1804 audit(1598924771.569:501): pid=8082 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir838623042/syzkaller.qsQEjl/51/bus" dev="sda1" ino=16496 res=1
audit: type=1804 audit(1598924771.599:502): pid=8082 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir838623042/syzkaller.qsQEjl/51/bus" dev="sda1" ino=16496 res=1
XFS (loop0): Invalid superblock magic number
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
IPVS: ftp: loaded support on port[0] = 21
block nbd3: Receive control failed (result -32)
block nbd3: Device being setup by another task
block nbd3: shutting down sockets
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
kauditd_printk_skb: 4 callbacks suppressed
audit: type=1800 audit(1598924775.049:507): pid=8266 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=16502 res=0
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
IPVS: ftp: loaded support on port[0] = 21
audit: type=1326 audit(1598924775.409:508): auid=0 uid=0 gid=0 ses=4 subj=system_u:system_r:kernel_t:s0 pid=8318 comm="syz-executor.1" exe="/root/syz-executor.1" sig=9 arch=c000003e syscall=228 compat=0 ip=0x4603fa code=0x0
device lo left promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): bridge0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
8021q: adding VLAN 0 to HW filter on device bond0
IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
8021q: adding VLAN 0 to HW filter on device team0
chnl_net:chnl_net_open(): err: Unable to register and open device, Err:-19
caif:caif_disconnect_client(): nothing to disconnect
audit: type=1326 audit(1598924776.199:509): auid=0 uid=0 gid=0 ses=4 subj=system_u:system_r:kernel_t:s0 pid=8318 comm="syz-executor.1" exe="/root/syz-executor.1" sig=9 arch=c000003e syscall=228 compat=0 ip=0x4603fa code=0x0
chnl_net:chnl_flowctrl_cb(): NET flowctrl func called flow: CLOSE/DEINIT
chnl_net:chnl_net_open(): state disconnected
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
skbuff: skb_over_panic: text:ffffffff858be28f len:40 put:40 head:ffff88809214d040 data:ffff88809214d0f0 tail:0xd8 end:0xc0 dev:ip6gre0
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:104!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 18 Comm: kworker/1:0 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_dad_work
task: ffff8880a98fe4c0 task.stack: ffff8880a9910000
RIP: 0010:skb_panic+0x172/0x174 net/core/skbuff.c:104
RSP: 0018:ffff8880a99178d0 EFLAGS: 00010282
RAX: 0000000000000086 RBX: ffff8880986dc300 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac12c0 RDI: ffffed1015322f10
RBP: ffffffff8738bba0 R08: 0000000000000086 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880a98fe4c0 R12: ffffffff858be28f
R13: 0000000000000028 R14: ffff888095548640 R15: 00000000000000c0
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa5b4050000 CR3: 000000008c904000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
skb_over_panic net/core/skbuff.c:109 [inline]
skb_put.cold+0x24/0x24 net/core/skbuff.c:1699
ip6_mc_hdr.constprop.0+0x11f/0x580 net/ipv6/mcast.c:1552
mld_newpack+0x3aa/0x720 net/ipv6/mcast.c:1603
add_grhead+0x265/0x330 net/ipv6/mcast.c:1691
add_grec+0xc40/0xed0 net/ipv6/mcast.c:1822
mld_send_initial_cr.part.0+0xb0/0x140 net/ipv6/mcast.c:2072
mld_send_initial_cr net/ipv6/mcast.c:1170 [inline]
ipv6_mc_dad_complete+0x183/0x5a0 net/ipv6/mcast.c:2084
addrconf_dad_completed+0x80f/0xa40 net/ipv6/addrconf.c:4060
addrconf_dad_begin net/ipv6/addrconf.c:3848 [inline]
addrconf_dad_work+0x673/0xef0 net/ipv6/addrconf.c:3950
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 8b 4c 24 10 8b 8b 80 00 00 00 41 56 45 89 e8 4c 89 e2 41 57 48 89 ee 48 c7 c7 40 b4 38 87 ff 74 24 10 ff 74 24 20 e8 95 68 3a fc <0f> 0b e8 2d c9 4b fc 4c 8b 64 24 18 e8 d3 7d 75 fc 48 c7 c1 60
RIP: skb_panic+0x172/0x174 net/core/skbuff.c:104 RSP: ffff8880a99178d0
---[ end trace 4519f45a536d5388 ]---
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1407a279900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=f6d6eb54399925b08415
compiler: gcc (GCC) 10.1.0-syz 20200507
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+f6d6eb...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
4.14.195-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.0/7679 is trying to acquire lock:
(&team->lock){+.+.}, at: [<ffffffff83e460b8>] team_vlan_rx_add_vid+0x38/0x1d0 drivers/net/team/team.c:1889
but task is already holding lock:
(&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by syz-executor.0/7679:
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnetlink_rcv_msg+0x31d/0xb10 net/core/rtnetlink.c:4311
#1: (&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
stack backtrace:
CPU: 0 PID: 7679 Comm: syz-executor.0 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_deadlock_bug kernel/locking/lockdep.c:1800 [inline]
check_deadlock kernel/locking/lockdep.c:1847 [inline]
validate_chain kernel/locking/lockdep.c:2448 [inline]
__lock_acquire.cold+0x180/0x97c kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
team_vlan_rx_add_vid+0x38/0x1d0 drivers/net/team/team.c:1889
__vlan_vid_add net/8021q/vlan_core.c:219 [inline]
vlan_vid_add+0x5ef/0x7d0 net/8021q/vlan_core.c:251
__vlan_vid_add net/8021q/vlan_core.c:219 [inline]
vlan_vid_add+0x5ef/0x7d0 net/8021q/vlan_core.c:251
vlan_device_event.cold+0x23/0x28 net/8021q/vlan.c:372
notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93
call_netdevice_notifiers_info net/core/dev.c:1667 [inline]
call_netdevice_notifiers net/core/dev.c:1683 [inline]
dev_open net/core/dev.c:1407 [inline]
dev_open+0xf9/0x110 net/core/dev.c:1395
team_port_add drivers/net/team/team.c:1214 [inline]
team_add_slave+0x954/0x1ad0 drivers/net/team/team.c:1968
do_set_master+0x19e/0x200 net/core/rtnetlink.c:1961
rtnl_newlink+0x134c/0x1830 net/core/rtnetlink.c:2757
rtnetlink_rcv_msg+0x3be/0xb10 net/core/rtnetlink.c:4316
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45d5b9
RSP: 002b:00007f02dd5d6c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002ce80 RCX: 000000000045d5b9
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffd3d2a361f R14: 00007f02dd5d79c0 R15: 000000000118cf4c
team0: Device macvtap1 failed to register rx_handler
audit: type=1804 audit(1598924767.179:493): pid=7692 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
audit: type=1804 audit(1598924767.409:494): pid=7710 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir610673552/syzkaller.i9eLlq/156/file0" dev="sda1" ino=16457 res=1
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
team0: Device macvtap1 failed to register rx_handler
audit: type=1804 audit(1598924767.419:495): pid=7710 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir610673552/syzkaller.i9eLlq/156/file0" dev="sda1" ino=16457 res=1
audit: type=1804 audit(1598924767.639:496): pid=7692 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
audit: type=1804 audit(1598924767.639:497): pid=7732 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir843860058/syzkaller.E4B1Cx/935/bus" dev="sda1" ino=17234 res=1
8021q: adding VLAN 0 to HW filter on device macvtap1
team0: Device macvtap1 failed to register rx_handler
REISERFS warning (device loop3): super-6508 reiserfs_parse_options: bad value 0x0000000000000000= for -ocommit
IPVS: ftp: loaded support on port[0] = 21
BFS-fs: bfs_fill_super(): Inode 0x00000026 corrupted
BFS-fs: bfs_fill_super(): Inode 0x00000026 corrupted
attempt to access beyond end of device
loop5: rw=1, want=230, limit=127
ip6_tables: ip6tables: counters copy to user failed while replacing table
new mount options do not match the existing superblock, will be ignored
hfs: dir_umask requires a value
ip6_tables: ip6tables: counters copy to user failed while replacing table
hfs: unable to parse mount options
new mount options do not match the existing superblock, will be ignored
ip6_tables: ip6tables: counters copy to user failed while replacing table
audit: type=1804 audit(1598924769.559:498): pid=7918 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir179861148/syzkaller.xjkBIl/269/bus" dev="sda1" ino=16471 res=1
ip6_tables: ip6tables: counters copy to user failed while replacing table
audit: type=1804 audit(1598924769.559:499): pid=7917 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir179861148/syzkaller.xjkBIl/269/bus" dev="sda1" ino=16471 res=1
audit: type=1800 audit(1598924769.609:500): pid=7866 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=16464 res=0
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
IPVS: ftp: loaded support on port[0] = 21
IPVS: length: 209 != 8
9pnet: Insufficient options for proto=fd
overlayfs: filesystem on './file0' not supported as upperdir
audit: type=1804 audit(1598924771.569:501): pid=8082 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir838623042/syzkaller.qsQEjl/51/bus" dev="sda1" ino=16496 res=1
audit: type=1804 audit(1598924771.599:502): pid=8082 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir838623042/syzkaller.qsQEjl/51/bus" dev="sda1" ino=16496 res=1
XFS (loop0): Invalid superblock magic number
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
IPVS: ftp: loaded support on port[0] = 21
block nbd3: Receive control failed (result -32)
block nbd3: Device being setup by another task
block nbd3: shutting down sockets
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
kauditd_printk_skb: 4 callbacks suppressed
audit: type=1800 audit(1598924775.049:507): pid=8266 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=16502 res=0
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
IPVS: ftp: loaded support on port[0] = 21
audit: type=1326 audit(1598924775.409:508): auid=0 uid=0 gid=0 ses=4 subj=system_u:system_r:kernel_t:s0 pid=8318 comm="syz-executor.1" exe="/root/syz-executor.1" sig=9 arch=c000003e syscall=228 compat=0 ip=0x4603fa code=0x0
device lo left promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): bridge0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
8021q: adding VLAN 0 to HW filter on device bond0
IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
8021q: adding VLAN 0 to HW filter on device team0
chnl_net:chnl_net_open(): err: Unable to register and open device, Err:-19
caif:caif_disconnect_client(): nothing to disconnect
audit: type=1326 audit(1598924776.199:509): auid=0 uid=0 gid=0 ses=4 subj=system_u:system_r:kernel_t:s0 pid=8318 comm="syz-executor.1" exe="/root/syz-executor.1" sig=9 arch=c000003e syscall=228 compat=0 ip=0x4603fa code=0x0
chnl_net:chnl_flowctrl_cb(): NET flowctrl func called flow: CLOSE/DEINIT
chnl_net:chnl_net_open(): state disconnected
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
skbuff: skb_over_panic: text:ffffffff858be28f len:40 put:40 head:ffff88809214d040 data:ffff88809214d0f0 tail:0xd8 end:0xc0 dev:ip6gre0
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:104!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 18 Comm: kworker/1:0 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_dad_work
task: ffff8880a98fe4c0 task.stack: ffff8880a9910000
RIP: 0010:skb_panic+0x172/0x174 net/core/skbuff.c:104
RSP: 0018:ffff8880a99178d0 EFLAGS: 00010282
RAX: 0000000000000086 RBX: ffff8880986dc300 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac12c0 RDI: ffffed1015322f10
RBP: ffffffff8738bba0 R08: 0000000000000086 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880a98fe4c0 R12: ffffffff858be28f
R13: 0000000000000028 R14: ffff888095548640 R15: 00000000000000c0
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa5b4050000 CR3: 000000008c904000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
skb_over_panic net/core/skbuff.c:109 [inline]
skb_put.cold+0x24/0x24 net/core/skbuff.c:1699
ip6_mc_hdr.constprop.0+0x11f/0x580 net/ipv6/mcast.c:1552
mld_newpack+0x3aa/0x720 net/ipv6/mcast.c:1603
add_grhead+0x265/0x330 net/ipv6/mcast.c:1691
add_grec+0xc40/0xed0 net/ipv6/mcast.c:1822
mld_send_initial_cr.part.0+0xb0/0x140 net/ipv6/mcast.c:2072
mld_send_initial_cr net/ipv6/mcast.c:1170 [inline]
ipv6_mc_dad_complete+0x183/0x5a0 net/ipv6/mcast.c:2084
addrconf_dad_completed+0x80f/0xa40 net/ipv6/addrconf.c:4060
addrconf_dad_begin net/ipv6/addrconf.c:3848 [inline]
addrconf_dad_work+0x673/0xef0 net/ipv6/addrconf.c:3950
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 8b 4c 24 10 8b 8b 80 00 00 00 41 56 45 89 e8 4c 89 e2 41 57 48 89 ee 48 c7 c7 40 b4 38 87 ff 74 24 10 ff 74 24 20 e8 95 68 3a fc <0f> 0b e8 2d c9 4b fc 4c 8b 64 24 18 e8 d3 7d 75 fc 48 c7 c1 60
RIP: skb_panic+0x172/0x174 net/core/skbuff.c:104 RSP: ffff8880a99178d0
---[ end trace 4519f45a536d5388 ]---
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Aug 31, 2020, 11:15:19 PM8/31/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=163b5a1e900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c8a835900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f6d6eb...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
device team1 entered promiscuous mode
RIP: 0033:0x443759
RSP: 002b:00007ffd50bfd768 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000443759
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 000000306d616574 R08: 0000000001bbbbbb R09: 0000000001bbbbbb
R10: 0000000001bbbbbb R11: 0000000000000246 R12: 00007ffd50bfd780
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=f6d6eb54399925b08415
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132d1a71900000
dashboard link: https://syzkaller.appspot.com/bug?extid=f6d6eb54399925b08415
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c8a835900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f6d6eb...@syzkaller.appspotmail.com
device team1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
4.14.195-syzkaller #0 Not tainted
--------------------------------------------
syz-executor361/6366 is trying to acquire lock:
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
4.14.195-syzkaller #0 Not tainted
--------------------------------------------
(&team->lock){+.+.}, at: [<ffffffff83e460b8>] team_vlan_rx_add_vid+0x38/0x1d0 drivers/net/team/team.c:1889
but task is already holding lock:
(&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by syz-executor361/6366:
but task is already holding lock:
(&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnetlink_rcv_msg+0x31d/0xb10 net/core/rtnetlink.c:4311
#1: (&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
stack backtrace:
CPU: 0 PID: 6366 Comm: syz-executor361 Not tainted 4.14.195-syzkaller #0
#0: (rtnl_mutex){+.+.}, at: [<ffffffff85176d2d>] rtnetlink_rcv_msg+0x31d/0xb10 net/core/rtnetlink.c:4311
#1: (&team->lock){+.+.}, at: [<ffffffff83e4e57d>] team_add_slave+0x7d/0x1ad0 drivers/net/team/team.c:1967
stack backtrace:
RSP: 002b:00007ffd50bfd768 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000443759
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 000000306d616574 R08: 0000000001bbbbbb R09: 0000000001bbbbbb
R10: 0000000001bbbbbb R11: 0000000000000246 R12: 00007ffd50bfd780
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
syzbot
Sep 1, 2020, 2:26:21 PM9/1/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17c7acf5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=9a692947a2e5d37361db
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12092285900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9a6929...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
device team1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
4.19.142-syzkaller #0 Not tainted
--------------------------------------------
syz-executor185/6487 is trying to acquire lock:
000000001de11139 (&team->lock){+.+.}, at: team_vlan_rx_add_vid+0x38/0x1e0 drivers/net/team/team.c:1896
but task is already holding lock:
00000000c5ea76c1 (&team->lock){+.+.}, at: team_add_slave+0x98/0x1eb0 drivers/net/team/team.c:1975
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by syz-executor185/6487:
#0: 0000000040c831f1 (rtnl_mutex){+.+.}, at: rtnl_lock net/core/rtnetlink.c:77 [inline]
#0: 0000000040c831f1 (rtnl_mutex){+.+.}, at: rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4775
#1: 00000000c5ea76c1 (&team->lock){+.+.}, at: team_add_slave+0x98/0x1eb0 drivers/net/team/team.c:1975
stack backtrace:
CPU: 0 PID: 6487 Comm: syz-executor185 Not tainted 4.19.142-syzkaller #0
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
print_deadlock_bug kernel/locking/lockdep.c:1763 [inline]
check_deadlock kernel/locking/lockdep.c:1807 [inline]
validate_chain kernel/locking/lockdep.c:2403 [inline]
__lock_acquire.cold+0x121/0x57e kernel/locking/lockdep.c:3415
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__mutex_lock_common kernel/locking/mutex.c:925 [inline]
__mutex_lock+0xd7/0x1260 kernel/locking/mutex.c:1072
team_vlan_rx_add_vid+0x38/0x1e0 drivers/net/team/team.c:1896
vlan_add_rx_filter_info+0x13c/0x1c0 net/8021q/vlan_core.c:210
__vlan_vid_add net/8021q/vlan_core.c:278 [inline]
vlan_vid_add+0x3ee/0x7e0 net/8021q/vlan_core.c:308
vlan_add_rx_filter_info+0x13c/0x1c0 net/8021q/vlan_core.c:210
__vlan_vid_add net/8021q/vlan_core.c:278 [inline]
vlan_vid_add+0x3ee/0x7e0 net/8021q/vlan_core.c:308
vlan_device_event.cold+0x28/0x2d net/8021q/vlan.c:381
notifier_call_chain+0xc0/0x230 kernel/notifier.c:93
call_netdevice_notifiers net/core/dev.c:1762 [inline]
dev_open net/core/dev.c:1442 [inline]
dev_open+0x128/0x140 net/core/dev.c:1430
team_port_add drivers/net/team/team.c:1220 [inline]
team_add_slave+0xa3c/0x1eb0 drivers/net/team/team.c:1976
do_set_master+0x1c8/0x220 net/core/rtnetlink.c:2321
rtnl_newlink+0x1270/0x15b0 net/core/rtnetlink.c:3170
rtnetlink_rcv_msg+0x453/0xb80 net/core/rtnetlink.c:4778
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x443759
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 fb 0f fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffef647faa8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following issue on:
HEAD commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17c7acf5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=9a692947a2e5d37361db
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115a4c35900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12092285900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
device team1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap1: link is not ready
8021q: adding VLAN 0 to HW filter on device macvtap1
============================================
WARNING: possible recursive locking detected
--------------------------------------------
syz-executor185/6487 is trying to acquire lock:
000000001de11139 (&team->lock){+.+.}, at: team_vlan_rx_add_vid+0x38/0x1e0 drivers/net/team/team.c:1896
but task is already holding lock:
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&team->lock);
lock(&team->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
#0: 0000000040c831f1 (rtnl_mutex){+.+.}, at: rtnl_lock net/core/rtnetlink.c:77 [inline]
#0: 0000000040c831f1 (rtnl_mutex){+.+.}, at: rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4775
#1: 00000000c5ea76c1 (&team->lock){+.+.}, at: team_add_slave+0x98/0x1eb0 drivers/net/team/team.c:1975
stack backtrace:
CPU: 0 PID: 6487 Comm: syz-executor185 Not tainted 4.19.142-syzkaller #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]
Call Trace:
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
print_deadlock_bug kernel/locking/lockdep.c:1763 [inline]
check_deadlock kernel/locking/lockdep.c:1807 [inline]
validate_chain kernel/locking/lockdep.c:2403 [inline]
__lock_acquire.cold+0x121/0x57e kernel/locking/lockdep.c:3415
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__mutex_lock_common kernel/locking/mutex.c:925 [inline]
__mutex_lock+0xd7/0x1260 kernel/locking/mutex.c:1072
team_vlan_rx_add_vid+0x38/0x1e0 drivers/net/team/team.c:1896
vlan_add_rx_filter_info+0x13c/0x1c0 net/8021q/vlan_core.c:210
__vlan_vid_add net/8021q/vlan_core.c:278 [inline]
vlan_vid_add+0x3ee/0x7e0 net/8021q/vlan_core.c:308
vlan_add_rx_filter_info+0x13c/0x1c0 net/8021q/vlan_core.c:210
__vlan_vid_add net/8021q/vlan_core.c:278 [inline]
vlan_vid_add+0x3ee/0x7e0 net/8021q/vlan_core.c:308
vlan_device_event.cold+0x28/0x2d net/8021q/vlan.c:381
notifier_call_chain+0xc0/0x230 kernel/notifier.c:93
call_netdevice_notifiers net/core/dev.c:1762 [inline]
dev_open net/core/dev.c:1442 [inline]
dev_open+0x128/0x140 net/core/dev.c:1430
team_port_add drivers/net/team/team.c:1220 [inline]
team_add_slave+0xa3c/0x1eb0 drivers/net/team/team.c:1976
do_set_master+0x1c8/0x220 net/core/rtnetlink.c:2321
rtnl_newlink+0x1270/0x15b0 net/core/rtnetlink.c:3170
rtnetlink_rcv_msg+0x453/0xb80 net/core/rtnetlink.c:4778
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x443759
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 fb 0f fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffef647faa8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000443759
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 000000306d616574 R08: 0000000001bbbbbb R09: 0000000001bbbbbb
R10: 0000000001bbbbbb R11: 0000000000000246 R12: 00007ffef647fac0
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 000000306d616574 R08: 0000000001bbbbbb R09: 0000000001bbbbbb
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
team0: Device macvtap1 failed to register rx_handler
team0: Device macvtap1 failed to register rx_handler
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages