BUG: receive list entry not found for dev vxcan1, id 003, mask C00007FF

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 470dfd80 lan743x: replace polling loop by wait_event_timeo..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f46c65500000
kernel config: https://syzkaller.appspot.com/x/.config?x=df65150a33f23d8c
dashboard link: https://syzkaller.appspot.com/bug?extid=76d62d3b8162883c7d11
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1164f8fd500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148ae72b500000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76d62d...@syzkaller.appspotmail.com

RAX: ffffffffffffffda RBX: 00007ffc766d7540 RCX: 0000000000443729
RDX: 0000000000000018 RSI: 0000000020000040 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000001bbbbbb
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffff
R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000000000
------------[ cut here ]------------
BUG: receive list entry not found for dev vxcan1, id 003, mask C00007FF
WARNING: CPU: 1 PID: 8479 at net/can/af_can.c:546 can_rx_unregister+0x5a4/0x700 net/can/af_can.c:546
Modules linked in:
CPU: 1 PID: 8479 Comm: syz-executor218 Not tainted 5.10.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:can_rx_unregister+0x5a4/0x700 net/can/af_can.c:546
Code: 8b 7c 24 78 44 8b 64 24 68 49 c7 c5 e0 de 56 8a e8 51 d3 95 f9 44 89 f9 44 89 e2 4c 89 ee 48 c7 c7 20 df 56 8a e8 a6 76 d3 00 <0f> 0b 48 8b 7c 24 28 e8 40 e9 0e 01 e9 54 fb ff ff e8 66 db d7 f9
RSP: 0018:ffffc900016ff9f0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff888020251a40 RSI: ffffffff8158f3c5 RDI: fffff520002dff30
RBP: 0000000000000118 R08: 0000000000000001 R09: ffff8880b9f30627
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
R13: ffff88802c1c0000 R14: 1ffff920002dff45 R15: 00000000c00007ff
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004c8908 CR3: 000000000b08e000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
isotp_notifier+0x2a7/0x540 net/can/isotp.c:1303
call_netdevice_notifier net/core/dev.c:1735 [inline]
call_netdevice_unregister_notifiers+0x156/0x1c0 net/core/dev.c:1763
call_netdevice_unregister_net_notifiers net/core/dev.c:1791 [inline]
unregister_netdevice_notifier+0xcd/0x170 net/core/dev.c:1870
isotp_release+0x136/0x600 net/can/isotp.c:1011
__sock_release+0xcd/0x280 net/socket.c:596
sock_close+0x18/0x20 net/socket.c:1255
__fput+0x285/0x920 fs/file_table.c:281
task_work_run+0xdd/0x190 kernel/task_work.c:151
exit_task_work include/linux/task_work.h:30 [inline]
do_exit+0xb64/0x29b0 kernel/exit.c:809
do_group_exit+0x125/0x310 kernel/exit.c:906
__do_sys_exit_group kernel/exit.c:917 [inline]
__se_sys_exit_group kernel/exit.c:915 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:915
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x442368
Code: Unable to access opcode bytes at RIP 0x44233e.
RSP: 002b:00007ffc766d74a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000000000442368
RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
RBP: 00000000004c88d0 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006dd240 R14: 0000000000000000 R15: 0000000000000000


---
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:
https://goo.gl/tpsmEJ#testing-patches