general protection fault in rlb_req_update_slave_clients

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 17529385 Linux 4.14.213
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=142a70c7500000
kernel config: https://syzkaller.appspot.com/x/.config?x=f94010bb59bd4675
dashboard link: https://syzkaller.appspot.com/bug?extid=114770a7da088491fdf4
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+114770...@syzkaller.appspotmail.com

RBP: 00007fb87fbe4ca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000009
R13: 00007ffd992fec7f R14: 00007fb87fbe59c0 R15: 000000000119c0dc
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 24595 Comm: syz-executor.3 Not tainted 4.14.213-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888022b4e0c0 task.stack: ffff888022b68000
RIP: 0010:rlb_req_update_slave_clients+0xeb/0x250 drivers/net/bonding/bond_alb.c:521
RSP: 0018:ffff888022b6ed48 EFLAGS: 00010206
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: ffffc900134d1000
RDX: 0000000000000006 RSI: ffffffff83d97474 RDI: 0000000000000030
RBP: ffff88803e3616c0 R08: ffffffff8b9a36b0 R09: 0000000000040983
R10: ffff888022b4e998 R11: ffff888022b4e0c0 R12: ffff88802587e4c0
R13: ffffed1007c6c2fa R14: 0000000000000000 R15: ffff88803e361700
FS: 00007fb87fbe5700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1b8b2c6db8 CR3: 0000000048168000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
alb_fasten_mac_swap+0x615/0x770 drivers/net/bonding/bond_alb.c:1082
bond_alb_set_mac_address+0x352/0x6d0 drivers/net/bonding/bond_alb.c:1793
bond_set_mac_address+0x61b/0x730 drivers/net/bonding/bond_main.c:3738
dev_set_mac_address+0x153/0x2d0 net/core/dev.c:6958
__set_port_dev_addr+0xe6/0x120 drivers/net/team/team.c:67
team_port_set_orig_dev_addr drivers/net/team/team.c:72 [inline]
team_port_add drivers/net/team/team.c:1313 [inline]
team_add_slave+0xad8/0x1bc0 drivers/net/team/team.c:1968
do_set_master+0x19e/0x200 net/core/rtnetlink.c:1961
do_setlink+0x8b8/0x2bf0 net/core/rtnetlink.c:2098
rtnl_newlink+0x1267/0x1830 net/core/rtnetlink.c:2660
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:0x45e219
RSP: 002b:00007fb87fbe4c68 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 000000000045e219
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000007
RBP: 00007fb87fbe4ca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000009
R13: 00007ffd992fec7f R14: 00007fb87fbe59c0 R15: 000000000119c0dc
Code: 2c cb 7d fd 41 80 7d 00 00 0f 85 36 01 00 00 44 89 f0 48 c1 e0 06 48 03 85 10 01 00 00 48 8d 78 30 49 89 c6 48 89 fa 48 c1 ea 03 <80> 3c 1a 00 0f 85 29 01 00 00 4d 39 66 30 75 8d e8 f0 ca 7d fd
RIP: rlb_req_update_slave_clients+0xeb/0x250 drivers/net/bonding/bond_alb.c:521 RSP: ffff888022b6ed48
---[ end trace e0bd1293e828d460 ]---


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.