From: syzbot <syzbot+381d06e0c8eaacb8706f@syzkaller.appspotmail.com>
To: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, mkl@pengutronix.de,
netdev@vger.kernel.org, socketcan@hartkopp.net,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: receive list entry not found for dev vxcan1, id 002, mask C00007FF
Date: Wed, 25 Nov 2020 05:51:18 -0800 [thread overview]
Message-ID: <000000000000c6d7a205b4eeb89b@google.com> (raw)
In-Reply-To: <00000000000041019205b4c4e9ad@google.com>
syzbot has found a reproducer for 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=107c26a5500000
kernel config: https://syzkaller.appspot.com/x/.config?x=df65150a33f23d8c
dashboard link: https://syzkaller.appspot.com/bug?extid=381d06e0c8eaacb8706f
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12bcd669500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ecad3e500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+381d06e0c8eaacb8706f@syzkaller.appspotmail.com
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00000000004442a9
RDX: 0000000000000018 RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00007ffc870fdef0 R08: 0000000000000001 R09: 0000000001bbbbbb
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc870fdf00
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
------------[ cut here ]------------
BUG: receive list entry not found for dev vxcan1, id 002, mask C00007FF
WARNING: CPU: 0 PID: 8713 at net/can/af_can.c:546 can_rx_unregister+0x5a4/0x700 net/can/af_can.c:546
Modules linked in:
CPU: 0 PID: 8713 Comm: syz-executor284 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:ffffc90001b2fb38 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff888014db8000 RSI: ffffffff8158f3c5 RDI: fffff52000365f59
RBP: 0000000000000118 R08: 0000000000000001 R09: ffff8880b9e30627
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
R13: ffff8880261f0000 R14: 1ffff92000365f6e R15: 00000000c00007ff
FS: 0000000000807880(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004bdfc4 CR3: 0000000014c7c000 CR4: 00000000001506f0
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
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_user_mode_loop kernel/entry/common.c:164 [inline]
exit_to_user_mode_prepare+0x17e/0x1a0 kernel/entry/common.c:191
syscall_exit_to_user_mode+0x38/0x260 kernel/entry/common.c:266
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x403b20
Code: 01 f0 ff ff 0f 83 40 0d 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 83 3d 6d bc 2d 00 00 75 14 b8 03 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 14 0d 00 00 c3 48 83 ec 08 e8 7a 02 00 00
RSP: 002b:00007ffc870fdee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000403b20
RDX: 0000000000000018 RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00007ffc870fdef0 R08: 0000000000000001 R09: 0000000001bbbbbb
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc870fdf00
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
next prev parent reply other threads:[~2020-11-25 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 11:58 BUG: receive list entry not found for dev vxcan1, id 002, mask C00007FF syzbot
2020-11-25 13:51 ` syzbot [this message]
2020-11-25 16:03 ` Oliver Hartkopp
2020-11-25 18:48 ` Dmitry Vyukov
2020-11-25 20:54 ` Oliver Hartkopp
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=000000000000c6d7a205b4eeb89b@google.com \
--to=syzbot+381d06e0c8eaacb8706f@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=syzkaller-bugs@googlegroups.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).