BUG: unable to handle kernel paging request in asm_call_on_stack

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88825726 Merge tag 'drm-fixes-2020-07-17-1' of git://anong..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a9ffbf100000
kernel config: https://syzkaller.appspot.com/x/.config?x=a160d1053fc89af5
dashboard link: https://syzkaller.appspot.com/bug?extid=aabbc7f07402d99c5a6a
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [b...@alien8.de h...@zytor.com linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com pet...@infradead.org tg...@linutronix.de tony...@intel.com x...@kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+aabbc7...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffffc90000007ff8
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD aa127067 P4D aa127067 PUD aa128067 PMD aa129067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6817 Comm: syz-executor.0 Not tainted 5.8.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:asm_call_on_stack+0x4/0x20 arch/x86/entry/entry_64.S:701
Code: 0f 1f 00 5f 48 89 c4 58 eb a3 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 01 f8 8e ef 0f 1f 00 0f 01 f8 c3 0f 1f 40 00 55 48 89 e5 <48> 89 27 48 89 fc 48 89 d7 ff d6 c9 c3 0f 1f 44 00 00 66 2e 0f 1f
RSP: 0018:ffffc90001657788 EFLAGS: 00010056
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001
RDX: ffffc900016577b8 RSI: ffffffff8130ad70 RDI: ffffc90000007ff8
RBP: ffffc90001657788 R08: ffffffff8be78018 R09: ffffffff8be7800f
R10: ffffffff8be78017 R11: 0000000000000001 R12: ffffc90000008000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000028e4940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000007ff8 CR3: 0000000097670000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__run_on_irqstack arch/x86/include/asm/irq_stack.h:22 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:48 [inline]
sysvec_apic_timer_interrupt+0xe0/0x120 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:587
RIP: 0010:check_kcov_mode kernel/kcov.c:165 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x2a/0x60 kernel/kcov.c:197
Code: 65 48 8b 14 25 00 ff 01 00 65 8b 05 b0 44 8e 7e a9 00 01 ff 00 48 8b 34 24 74 0f f6 c4 01 74 35 8b 82 04 14 00 00 85 c0 74 2b <8b> 82 e0 13 00 00 83 f8 02 75 20 48 8b 8a e8 13 00 00 8b 92 e4 13
RSP: 0018:ffffc90001657860 EFLAGS: 00000246
RAX: 0000000080000000 RBX: 0000000000000000 RCX: ffffffff83628c67
RDX: ffff88808e1985c0 RSI: ffffffff83628c7a RDI: 0000000000000005
RBP: ffff8880a8a8ca80 R08: 0000000000000001 R09: ffffffff8cac36e7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000004
R13: 0000000000000053 R14: dffffc0000000000 R15: 0000000000000000
tomoyo_domain_quota_is_ok+0x31a/0x550 security/tomoyo/util.c:1070
tomoyo_supervisor+0x2d4/0xeb0 security/tomoyo/common.c:2089
tomoyo_audit_path_log security/tomoyo/file.c:168 [inline]
tomoyo_path_permission security/tomoyo/file.c:587 [inline]
tomoyo_path_permission+0x25c/0x360 security/tomoyo/file.c:573
tomoyo_path_perm+0x2e7/0x3f0 security/tomoyo/file.c:838
security_inode_getattr+0xcf/0x140 security/security.c:1278
vfs_getattr fs/stat.c:121 [inline]
vfs_statx+0x170/0x390 fs/stat.c:206
vfs_lstat include/linux/fs.h:3302 [inline]
__do_sys_newlstat+0x91/0x110 fs/stat.c:374
do_syscall_64+0x60/0xe0 arch/x86/entry/common.c:384
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45b5f5
Code: Bad RIP value.
RSP: 002b:00007fffeef6aea8 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000045b5f5
RDX: 00007fffeef6aec0 RSI: 00007fffeef6aec0 RDI: 00007fffeef6af50
RBP: 00000000000011ca R08: 0000000000000000 R09: 000000000000000d
R10: 0000000000000006 R11: 0000000000000246 R12: 00007fffeef6bfe0
R13: 00000000028e5940 R14: 0000000000000000 R15: 00007fffeef6bfe0
Modules linked in:
CR2: ffffc90000007ff8
---[ end trace 67b905577b6e7611 ]---
RIP: 0010:asm_call_on_stack+0x4/0x20 arch/x86/entry/entry_64.S:701
Code: 0f 1f 00 5f 48 89 c4 58 eb a3 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 01 f8 8e ef 0f 1f 00 0f 01 f8 c3 0f 1f 40 00 55 48 89 e5 <48> 89 27 48 89 fc 48 89 d7 ff d6 c9 c3 0f 1f 44 00 00 66 2e 0f 1f
RSP: 0018:ffffc90001657788 EFLAGS: 00010056
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001
RDX: ffffc900016577b8 RSI: ffffffff8130ad70 RDI: ffffc90000007ff8
RBP: ffffc90001657788 R08: ffffffff8be78018 R09: ffffffff8be7800f
R10: ffffffff8be78017 R11: 0000000000000001 R12: ffffc90000008000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000028e4940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000007ff8 CR3: 0000000097670000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status 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.