From: syzbot <syzbot+0d294e1d3ade13a70161@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, j.vosburgh@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
vfalico@gmail.com
Subject: [syzbot] WARNING in bond_update_slave_arr (2)
Date: Mon, 17 May 2021 04:48:17 -0700 [thread overview]
Message-ID: <000000000000584fd505c2852b25@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1678e493 Merge tag 'lto-v5.12-rc6' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146488fcd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1a3d65a48dbd1bc
dashboard link: https://syzkaller.appspot.com/bug?extid=0d294e1d3ade13a70161
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+0d294e1d3ade13a70161@syzkaller.appspotmail.com
netlink: 'syz-executor.0': attribute type 1 has an invalid length.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 21400 at drivers/net/bonding/bond_main.c:4395 bond_update_slave_arr+0xcb0/0x10c0 drivers/net/bonding/bond_main.c:4395
Modules linked in:
CPU: 0 PID: 21400 Comm: syz-executor.0 Not tainted 5.12.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bond_update_slave_arr+0xcb0/0x10c0 drivers/net/bonding/bond_main.c:4395
Code: cb fc 45 31 e4 e9 76 fe ff ff e8 eb bc cb fc 48 83 3c 24 00 41 bc f4 ff ff ff 0f 85 67 fc ff ff e9 7f fe ff ff e8 d0 bc cb fc <0f> 0b e9 e7 f3 ff ff e8 c4 bc cb fc 48 85 ed 41 bc f4 ff ff ff 0f
RSP: 0018:ffffc90001bbee38 EFLAGS: 00010216
RAX: 000000000002a883 RBX: ffff88807b5d0c00 RCX: ffffc90009192000
RDX: 0000000000040000 RSI: ffffffff84a83480 RDI: 0000000000000003
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff84a82866 R11: 0000000000000001 R12: 0000000000000006
R13: ffff88807b5d0038 R14: 0000000000000000 R15: ffff88807b5d0c00
FS: 00007f3c00d35700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f00387e3000 CR3: 000000007af5a000 CR4: 0000000000350ef0
Call Trace:
bond_open+0x448/0xc00 drivers/net/bonding/bond_main.c:3710
__dev_open+0x2bc/0x4d0 net/core/dev.c:1563
__dev_change_flags+0x583/0x750 net/core/dev.c:8686
rtnl_configure_link+0xee/0x240 net/core/rtnetlink.c:3125
__rtnl_newlink+0x1093/0x1710 net/core/rtnetlink.c:3451
rtnl_newlink+0x64/0xa0 net/core/rtnetlink.c:3491
rtnetlink_rcv_msg+0x44e/0xad0 net/core/rtnetlink.c:5553
netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2502
netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338
netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927
sock_sendmsg_nosec net/socket.c:654 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:674
____sys_sendmsg+0x6e8/0x810 net/socket.c:2350
___sys_sendmsg+0xf3/0x170 net/socket.c:2404
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2433
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x466459
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3c00d35188 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000466459
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00000000004bf9fb R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007fff04d9e05f R14: 00007f3c00d35300 R15: 0000000000022000
---
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.
reply other threads:[~2021-05-17 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000584fd505c2852b25@google.com \
--to=syzbot+0d294e1d3ade13a70161@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vfalico@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).