From: syzbot <syzbot+b0a18ed7b08b735d2f41@syzkaller.appspotmail.com>
To: davem@davemloft.net, jiri@mellanox.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: WARNING in devlink_port_type_warn
Date: Fri, 08 Nov 2019 00:58:08 -0800 [thread overview]
Message-ID: <0000000000001677ca0596d1fb43@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: c68c5373 Add linux-next specific files for 20191107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10b177fae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=742545dcdea21726
dashboard link: https://syzkaller.appspot.com/bug?extid=b0a18ed7b08b735d2f41
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+b0a18ed7b08b735d2f41@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.0009: unknown main item tag 0x0
hid-generic 0000:0000:0000.0009: unknown main item tag 0x0
hid-generic 0000:0000:0000.0009: hidraw0: <UNKNOWN> HID v0.00 Device [syz1]
on syz1
------------[ cut here ]------------
Type was not set for devlink port.
WARNING: CPU: 1 PID: 50 at net/core/devlink.c:6342
devlink_port_type_warn+0x15/0x20 net/core/devlink.c:6342
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 50 Comm: kworker/1:1 Not tainted 5.4.0-rc6-next-20191107 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: events devlink_port_type_warn
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x197/0x210 lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:221
__warn.cold+0x2f/0x35 kernel/panic.c:582
report_bug+0x289/0x300 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:267
do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:devlink_port_type_warn+0x15/0x20 net/core/devlink.c:6342
Code: 89 df e8 de 44 ec fb e9 d3 fe ff ff 66 0f 1f 84 00 00 00 00 00 55 48
89 e5 e8 f7 19 b0 fb 48 c7 c7 e0 ef 4a 88 e8 63 2b 81 fb <0f> 0b 5d c3 0f
1f 80 00 00 00 00 55 48 89 e5 41 55 49 89 f5 41 54
RSP: 0018:ffff8880a9b07d30 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815d0b86 RDI: ffffed1015360f98
RBP: ffff8880a9b07d30 R08: ffff8880a9b365c0 R09: fffffbfff14f374c
R10: fffffbfff14f374b R11: ffffffff8a79ba5f R12: ffff888076daecc0
R13: 0000000000000080 R14: ffff8880a99aa900 R15: ffff8880ae934540
process_one_work+0x9af/0x1740 kernel/workqueue.c:2263
worker_thread+0x98/0xe40 kernel/workqueue.c:2409
kthread+0x361/0x430 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2019-11-08 8:58 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=0000000000001677ca0596d1fb43@google.com \
--to=syzbot+b0a18ed7b08b735d2f41@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.