BUG: unable to handle kernel NULL pointer dereference at (null)

[syzbot]

Hello,

syzkaller hit the following crash on
9458bf6edfa820c6a4eea26bfd80ad05425aa58f
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.


CC: [john....@linaro.org linux-...@vger.kernel.org
sb...@codeaurora.org tg...@linutronix.de]

BUG: unable to handle kernel NULL pointer dereference at (null)
IP: (null)
PGD 3dfc3067
P4D 3dfc3067
PUD 3dffa067
PMD 0

Oops: 0010 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 2 PID: 17825 Comm: syz-executor5 Not tainted 4.13.0-rc7-next-20170829+
#11
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
task: ffff8800579c8280 task.stack: ffff880058bb0000
RIP: 0010: (null)
RSP: 0018:ffff88006de078c0 EFLAGS: 00010206
RAX: 0000000000000000 RBX: 1ffff1000dbc0f1e RCX: 0000000000000000
RDX: 0000000000000100 RSI: ffffffff85b386a0 RDI: 0000000000000000
RBP: ffff88006de07a98 R08: ffff88006de07230 R09: ffff88006de07228
R10: ffff88006de071a0 R11: 1ffff1000af392e3 R12: ffff88006de07a70
R13: ffff88006cc73b00 R14: 0000000000000102 R15: ffff88006de07a10
FS: 00007f07a0958700(0000) GS:ffff88006de00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000039156000 CR4: 00000000000026e0
DR0: 0000000020000000 DR1: 0000000020001000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
expire_timers kernel/time/timer.c:1320 [inline]
__run_timers+0x7fd/0xb90 kernel/time/timer.c:1620
run_timer_softirq+0x4c/0xb0 kernel/time/timer.c:1646
__do_softirq+0x2bd/0xbd4 kernel/softirq.c:284
invoke_softirq kernel/softirq.c:364 [inline]
irq_exit+0x1d3/0x210 kernel/softirq.c:405
exiting_irq arch/x86/include/asm/apic.h:638 [inline]
smp_apic_timer_interrupt+0x76/0xa0 arch/x86/kernel/apic/apic.c:1044
apic_timer_interrupt+0x9d/0xb0 arch/x86/entry/entry_64.S:577
</IRQ>
RIP: 0010:rep_nop arch/x86/include/asm/processor.h:634 [inline]
RIP: 0010:cpu_relax arch/x86/include/asm/processor.h:639 [inline]
RIP: 0010:mutex_spin_on_owner+0x1e2/0x970 kernel/locking/mutex.c:453
RSP: 0018:ffff880058bb6f18 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff10
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: ffffed000af39050
RDX: ffff880058bb6ff8 RSI: ffff880056d5e1e0 RDI: 0000000000000001
RBP: ffff880058bb7060 R08: ffff8800579c8280 R09: ffffffff81537100
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff85b92660
R13: ffff880056d5e180 R14: ffff880058bb7038 R15: 1ffff1000b176deb
mutex_optimistic_spin kernel/locking/mutex.c:547 [inline]
__mutex_lock_common kernel/locking/mutex.c:759 [inline]
__mutex_lock+0x3b6/0x1870 kernel/locking/mutex.c:893
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
jump_label_lock kernel/jump_label.c:27 [inline]
static_key_slow_inc_cpuslocked kernel/jump_label.c:106 [inline]
static_key_slow_inc+0x211/0x3c0 kernel/jump_label.c:124
tracepoint_add_func kernel/tracepoint.c:223 [inline]
tracepoint_probe_register_prio+0x80d/0x9a0 kernel/tracepoint.c:283
tracepoint_probe_register+0x2a/0x40 kernel/tracepoint.c:304
trace_event_reg+0x167/0x320 kernel/trace/trace_events.c:305
perf_trace_event_reg kernel/trace/trace_event_perf.c:122 [inline]
perf_trace_event_init kernel/trace/trace_event_perf.c:197 [inline]
perf_trace_init+0x4f9/0xab0 kernel/trace/trace_event_perf.c:221
perf_tp_event_init+0x7d/0xf0 kernel/events/core.c:7986
perf_try_init_event+0xc9/0x1f0 kernel/events/core.c:9210
perf_init_event kernel/events/core.c:9248 [inline]
perf_event_alloc+0x1c15/0x2990 kernel/events/core.c:9507
SYSC_perf_event_open+0x7f3/0x2d90 kernel/events/core.c:9955
SyS_perf_event_open+0x39/0x50 kernel/events/core.c:9846
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x446749
RSP: 002b:00007f07a0957c08 EFLAGS: 00000282 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 000000002001d000 RCX: 0000000000446749
RDX: ffffffffffffffff RSI: 00000000000005ce RDI: 000000002001d000
RBP: 0000000000000086 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000282 R12: 00000000ffffffff
R13: 00000000000056f0 R14: 00000000006e77b0 R15: 0000000000000000
Code: Bad RIP value.
RIP: (null) RSP: ffff88006de078c0
CR2: 0000000000000000
---[ end trace b2a39d152c2beddf ]---


---
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.
Please credit me with: Reported-by: syzbot

syzbot will keep track of this bug report.
Once a fix for this bug is committed, 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.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

This looks like timers corruption, happened only once, let's write it
off onto the old tun bug:

#syz invalid

On Tue, Oct 31, 2017 at 1:44 PM, syzbot
<bot+b9a0253b13a038eacc...@syzkaller.appspotmail.com>
wrote:

> --
> 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 post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a1148e120e7a6a4055cd56e5a%40google.com.
> For more options, visit https://groups.google.com/d/optout.