WARNING in handle_irq

[syzbot]

Hello,

syzbot hit the following crash on net-next commit
f74290fdb363665538743d14c4f00aeacdb68d87 (Sat Feb 24 05:04:20 2018 +0000)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
CC: [b...@suse.de gre...@linuxfoundation.org h...@zytor.com
linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com
tg...@linutronix.de x...@kernel.org]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+f1562e...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

------------[ cut here ]------------
do_IRQ(): syz-executor2 has overflown the kernel stack
(cur:ffff8801aa890000,sp:ffff8801aa88d6c8,irq stk
top-bottom:ffff8801db300080-ffff8801db308000,exception stk
top-bottom:fffffe0000038080-fffffe0000042000,ip:_raw_spin_unlock_irqrestore+0x5e/0xba)
WARNING: CPU: 1 PID: 28339 at arch/x86/kernel/irq_64.c:63
stack_overflow_check arch/x86/kernel/irq_64.c:60 [inline]
WARNING: CPU: 1 PID: 28339 at arch/x86/kernel/irq_64.c:63
handle_irq+0x20b/0x300 arch/x86/kernel/irq_64.c:72
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 28339 Comm: syz-executor2 Not tainted 4.16.0-rc2+ #241
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x24d lib/dump_stack.c:53
panic+0x1e4/0x41c kernel/panic.c:183
__warn+0x1dc/0x200 kernel/panic.c:547
report_bug+0x211/0x2d0 lib/bug.c:184
fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:178
fixup_bug arch/x86/kernel/traps.c:247 [inline]
do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x58/0x80 arch/x86/entry/entry_64.S:957
RIP: 0010:stack_overflow_check arch/x86/kernel/irq_64.c:60 [inline]
RIP: 0010:handle_irq+0x20b/0x300 arch/x86/kernel/irq_64.c:72
RSP: 0018:ffff8801db307f58 EFLAGS: 00010082
RAX: dffffc0000000008 RBX: ffff8801d28f7200 RCX: ffffffff815abe7e
RDX: 0000000000010000 RSI: 1ffff1003b660f9b RDI: 1ffff1003b660f70
RBP: ffff8801db307fb0 R08: 0000000000000000 R09: 1ffff1003b660f42
R10: 1ffff10035511ad3 R11: 0000000000000015 R12: fffffe0000042000
R13: fffffe0000038080 R14: 000000000000002a R15: 0000000000000000
do_IRQ+0x78/0x190 arch/x86/kernel/irq.c:238
common_interrupt+0x8e/0x8e arch/x86/entry/entry_64.S:576
</IRQ>
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

Does not look actionable. Happened once 3 months ago.

#syz invalid

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a11425c9676dfd105666959f1%40google.com.
> For more options, visit https://groups.google.com/d/optout.