WARNING in switch_mm_irqs_off

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 9c48b1d116cd Merge branch 'bpf-arm-jit-improvements'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1614f978400000
kernel config: https://syzkaller.appspot.com/x/.config?x=a501a01deaf0fe9
dashboard link: https://syzkaller.appspot.com/bug?extid=ed6f536dccd5ad2b82db
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [dave....@linux.intel.com h...@zytor.com
kirill....@linux.intel.com linux-...@vger.kernel.org
lu...@kernel.org mathieu....@efficios.com mi...@redhat.com
pet...@infradead.org tg...@linutronix.de tim.c...@linux.intel.com
x...@kernel.org]

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+ed6f53...@syzkaller.appspotmail.com

sctp: [Deprecated]: syz-executor2 (pid 10567) Use of struct
sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor2 (pid 10567) Use of struct
sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:214 __read_cr3
arch/x86/include/asm/paravirt.h:67 [inline]
WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:214
switch_mm_irqs_off+0xdcb/0x16c0 arch/x86/mm/tlb.c:214
BUG: unable to handle kernel paging request at ffff8801aa596d38
Kernel panic - not syncing: panic_on_warn set ...

PGD b4e1067 P4D b4e1067 PUD 1b7bbf063 PMD 19be18063
==================================================================
BUG: KASAN: stack-out-of-bounds in pte_val
arch/x86/include/asm/paravirt.h:384 [inline]
BUG: KASAN: stack-out-of-bounds in dump_pagetable+0x95c/0x970
arch/x86/mm/fault.c:559
Read of size 8 at addr ffff88019be18cb0 by task syz-executor1/10555

CPU: 1 PID: 10555 Comm: syz-executor1 Not tainted 4.18.0-rc3+ #52
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
print_address_description+0x6c/0x20b mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433
pte_val arch/x86/include/asm/paravirt.h:384 [inline]
dump_pagetable+0x95c/0x970 arch/x86/mm/fault.c:559
show_fault_oops arch/x86/mm/fault.c:675 [inline]
no_context.cold.36+0x76/0x98 arch/x86/mm/fault.c:798
__bad_area_nosemaphore+0x33b/0x3f0 arch/x86/mm/fault.c:902
bad_area_nosemaphore+0x33/0x40 arch/x86/mm/fault.c:909
__do_page_fault+0x1db/0xe50 arch/x86/mm/fault.c:1328
do_page_fault+0xf6/0x8c0 arch/x86/mm/fault.c:1471
page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1160
RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline]
RIP: 0010:get_running_cputimer include/linux/sched/cputime.h:85 [inline]
RIP: 0010:account_group_system_time include/linux/sched/cputime.h:149
[inline]
RIP: 0010:account_system_index_time+0x10a/0x5c0 kernel/sched/cputime.c:168
Code: 00 48 8d 88 20 01 00 00 48 89 fe 48 c1 ee 03 0f b6 14 16 48 89 fe 83
e6 07 40 38 f2 7f 08 84 d2 0f 85 f9 03 00 00 4d 8d 67 80 <0f> b6 b0 38 01
00 00 48 ba 00 00 00 00 00 fc ff df 4c 89 e7 48 c1
RSP: 0018:ffff8801daf07988 EFLAGS: 00010046
RAX: ffff8801aa596c00 RBX: ffff8801ae8a4600 RCX: ffff8801aa596d20
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801aa596d38
RBP: ffff8801daf07a68 R08: ffff8801ae8a4600 R09: fffffbfff11f424c
R10: fffffbfff11c1b45 R11: ffffffff88fa1263 R12: ffff8801daf079c0
R13: 00000000000f4240 R14: 1ffff1003b5e0f34 R15: ffff8801daf07a40
account_system_time+0x7f/0xb0 kernel/sched/cputime.c:199
account_process_tick+0x76/0x240 kernel/sched/cputime.c:498
update_process_times+0x21/0x70 kernel/time/timer.c:1634
tick_sched_handle+0x9f/0x180 kernel/time/tick-sched.c:164
tick_sched_timer+0x45/0x130 kernel/time/tick-sched.c:1274
__run_hrtimer kernel/time/hrtimer.c:1398 [inline]
__hrtimer_run_queues+0x3eb/0x10c0 kernel/time/hrtimer.c:1460
hrtimer_interrupt+0x2f3/0x750 kernel/time/hrtimer.c:1518
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1025 [inline]
smp_apic_timer_interrupt+0x165/0x730 arch/x86/kernel/apic/apic.c:1050
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:863
</IRQ>

The buggy address belongs to the page:
page:ffffea00066f8600 count:1 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x2fffc0000000000()
raw: 02fffc0000000000 dead000000000100 dead000000000200 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff88019be18b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1
ffff88019be18c00: f1 f1 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2
> ffff88019be18c80: f2 f2 00 f2 f2 f2 f2 f2 f2 f2 f8 f2 f2 f2 f2 f2
^
ffff88019be18d00: f2 f2 00 f2 f2 f2 00 00 00 00 00 00 00 00 00 00
ffff88019be18d80: 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00
==================================================================
PTE ffffffff88bd5aa7
Thread overran stack, or stack corrupted
Oops: 0009 [#1] SMP KASAN
CPU: 1 PID: 10555 Comm: syz-executor1 Tainted: G B
4.18.0-rc3+ #52
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline]
RIP: 0010:get_running_cputimer include/linux/sched/cputime.h:85 [inline]
RIP: 0010:account_group_system_time include/linux/sched/cputime.h:149
[inline]
RIP: 0010:account_system_index_time+0x10a/0x5c0 kernel/sched/cputime.c:168
Code: 00 48 8d 88 20 01 00 00 48 89 fe 48 c1 ee 03 0f b6 14 16 48 89 fe 83
e6 07 40 38 f2 7f 08 84 d2 0f 85 f9 03 00 00 4d 8d 67 80 <0f> b6 b0 38 01
00 00 48 ba 00 00 00 00 00 fc ff df 4c 89 e7 48 c1
RSP: 0018:ffff8801daf07988 EFLAGS: 00010046
RAX: ffff8801aa596c00 RBX: ffff8801ae8a4600 RCX: ffff8801aa596d20
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801aa596d38
RBP: ffff8801daf07a68 R08: ffff8801ae8a4600 R09: fffffbfff11f424c
R10: fffffbfff11c1b45 R11: ffffffff88fa1263 R12: ffff8801daf079c0
R13: 00000000000f4240 R14: 1ffff1003b5e0f34 R15: ffff8801daf07a40
FS: 0000000001e96940(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8801aa596d38 CR3: 00000001ab001000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
account_system_time+0x7f/0xb0 kernel/sched/cputime.c:199
account_process_tick+0x76/0x240 kernel/sched/cputime.c:498
update_process_times+0x21/0x70 kernel/time/timer.c:1634
tick_sched_handle+0x9f/0x180 kernel/time/tick-sched.c:164
tick_sched_timer+0x45/0x130 kernel/time/tick-sched.c:1274
__run_hrtimer kernel/time/hrtimer.c:1398 [inline]
__hrtimer_run_queues+0x3eb/0x10c0 kernel/time/hrtimer.c:1460
hrtimer_interrupt+0x2f3/0x750 kernel/time/hrtimer.c:1518
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1025 [inline]
smp_apic_timer_interrupt+0x165/0x730 arch/x86/kernel/apic/apic.c:1050
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:863
</IRQ>
Modules linked in:
Dumping ftrace buffer:
---------------------------------
syz-exec-20866 1...2 161228705us : 0: }D
syz-exec-20866 1...2 161228713us : 0: }D
syz-exec-20866 1...2 161228715us : 0: }D
syz-exec-20866 1...2 161228718us : 0: }D
syz-exec-20866 1...2 161228721us : 0: }D
syz-exec-20866 1...2 161228723us : 0: }D
syz-exec-20866 1...2 161228726us : 0: }D
syz-exec-20866 1...2 161228728us : 0: }D
syz-exec-20866 1...2 161228731us : 0: }D
syz-exec-20866 1...2 161228733us : 0: }D
syz-exec-20866 1...2 161228736us : 0: }D
syz-exec-20866 1...2 161228738us : 0: }D
syz-exec-20866 1...2 161228741us : 0: }D
syz-exec-20866 1...2 161228743us : 0: }D
syz-exec-20866 1...2 161228746us : 0: }D
syz-exec-20866 1...2 161228748us : 0: }D
syz-exec-20866 1...2 161228750us : 0: }D
syz-exec-20866 1...2 161228752us : 0: }D
syz-exec-20866 1...2 161228755us : 0: }D
syz-exec-20866 1...2 161228757us : 0: }D
syz-exec-20866 1...2 161228759us : 0: }D
syz-exec-20866 1...2 161228762us : 0: }D
syz-exec-20866 1...2 161228764us : 0: }D
syz-exec-20866 1...2 161228767us : 0: }D
syz-exec-20866 1...2 161228769us : 0: }D
syz-exec-20866 1...2 161228772us : 0: }D
syz-exec-20866 1...2 161228774us : 0: }D
syz-exec-20866 1...2 161228777us : 0: }D
syz-exec-20866 1...2 161228779us : 0: }D
syz-exec-20866 1...2 161228782us : 0: }D
syz-exec-20866 1...2 161228784us : 0: }D
syz-exec-20866 1...2 161228787us : 0: }D
syz-exec-20866 1...2 161228789us : 0: }D
syz-exec-20866 1...2 161228792us : 0: }D
syz-exec-20866 1...2 161228794us : 0: }D
syz-exec-20866 1...2 161228797us : 0: }D
syz-exec-20866 1...2 161228799us : 0: }D
syz-exec-20866 1...2 161228802us : 0: }D
syz-exec-20866 1...2 161228805us : 0: }D
syz-exec-20866 1...2 161228807us : 0: }D
syz-exec-20866 1...2 161228810us : 0: }D
syz-exec-20866 1...2 161228812us : 0: }D
syz-exec-20866 1...2 161228814us : 0: }D
syz-exec-20866 1...2 161228817us : 0: }D
syz-exec-20866 1...2 161228819us : 0: }D
syz-exec-20866 1...2 161228822us : 0: }D
syz-exec-20866 1...2 161228824us : 0: }D
syz-exec-20866 1...2 161228827us : 0: }D
syz-exec-20866 1...2 161228830us : 0: }D
syz-exec-20866 1...2 161228832us : 0: }D
syz-exec-20866 1...2 161228835us : 0: }D
syz-exec-20866 1...2 161228838us : 0: }D
syz-exec-20866 1...2 161228840us : 0: }D


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.