linux-kernel - Re: BUG: unable to handle kernel paging request in try_to_wake

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZJidrPD7Dv_AB+5DE=H7c=7W9_+Eg_k9yT3Q0MO8XO=g@mail.gmail.com>
Date:   Tue, 19 Dec 2017 13:14:37 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     syzbot 
        <bot+394f8cb7e1b0136587190205ba0b0f613a814a22@...kaller.appspotmail.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        syzkaller-bugs@...glegroups.com
Subject: Re: BUG: unable to handle kernel paging request in try_to_wake_up

On Sun, Dec 3, 2017 at 3:27 PM, syzbot
<bot+394f8cb7e1b0136587190205ba0b0f613a814a22@...kaller.appspotmail.com>
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 5bef2980adef8a6032d4f4709aebe9486181052f
> 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.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> *** Guest State ***
> CR0: actual=0x0000000080000031, shadow=0x0000000060000010,
> gh_mask=fffffffffffffff7
> BUG: unable to handle kernel paging request at fffffffffffffff8
> IP: try_to_wake_up+0x140/0x1600 kernel/sched/core.c:2086
> PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0
> Oops: 0002 [#1] SMP KASAN
> Dumping ftrace buffer:
>    (ftrace buffer empty)
> Modules linked in:
> CPU: 0 PID: 16886 Comm: syz-executor2 Not tainted 4.15.0-rc1-next-20171128+
> #54
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> task: ffff8801ceada280 task.stack: ffff8801d1630000
> RIP: 0010:try_to_wake_up+0x140/0x1600 kernel/sched/core.c:2086
> RSP: 0018:ffff8801db407740 EFLAGS: 00010002
> RAX: 0000000000000001 RBX: 1ffff1003b680ef4 RCX: ffff8801d04aa408
> RDX: 1ffff1003a09557a RSI: 0000000000000001 RDI: ffff8801d04aabc4
> RBP: ffff8801db407928 R08: 0000000000000004 R09: 000000000000000c
> R10: 0000000000000000 R11: ffffffff8748cd60 R12: ffff8801db407900
> R13: ffff8801d04aabc0 R14: ffff8801d04aa400 R15: 0000000000000000
> FS:  00007f15dd482700(0000) GS:ffff8801db400000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: fffffffffffffff8 CR3: 00000001cb92f000 CR4: 00000000001426f0
> DR0: 0000000020001000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <IRQ>
>  default_wake_function+0x30/0x50 kernel/sched/core.c:3629
>  autoremove_wake_function+0x78/0x350 kernel/sched/wait.c:377
>  __wake_up_common+0x18e/0x780 kernel/sched/wait.c:97
>  __wake_up_common_lock+0x1b4/0x310 kernel/sched/wait.c:125
>  __wake_up+0xe/0x10 kernel/sched/wait.c:149
>  wake_up_klogd_work_func+0x4a/0x70 kernel/printk/printk.c:2699
>  irq_work_run_list+0x184/0x240 kernel/irq_work.c:155
>  irq_work_run+0x31/0x50 kernel/irq_work.c:171
>  flush_smp_call_function_queue+0x288/0x570 kernel/smp.c:257
>  generic_smp_call_function_single_interrupt+0x13/0x30 kernel/smp.c:192
>  smp_call_function_single_interrupt+0x103/0x640 arch/x86/kernel/smp.c:295
>  call_function_single_interrupt+0xa9/0xb0 arch/x86/entry/entry_64.S:929
>  </IRQ>
> RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:777
> [inline]
> RIP: 0010:console_unlock+0x954/0xd70 kernel/printk/printk.c:2235
> RSP: 0018:ffff8801d16372f8 EFLAGS: 00000212 ORIG_RAX: ffffffffffffff04
> RAX: 0000000000010000 RBX: 0000000000000000 RCX: ffffffff8159b46b
> RDX: 000000000000590e RSI: ffffc90002047000 RDI: 0000000000000212
> RBP: ffff8801d16373e0 R08: 1ffff1003a2c6e2d R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 0000000000000000 R14: dffffc0000000000 R15: ffffffff83a22180
>  vprintk_emit+0x4ad/0x590 kernel/printk/printk.c:1757
>  vprintk_default+0x28/0x30 kernel/printk/printk.c:1796
>  vprintk_func+0x57/0xc0 kernel/printk/printk_safe.c:379
>  printk+0xaa/0xca kernel/printk/printk.c:1829
>  dump_vmcs arch/x86/kvm/vmx.c:8675 [inline]
>  vmx_handle_exit+0xbee/0x1ce0 arch/x86/kvm/vmx.c:8830
>  vcpu_enter_guest arch/x86/kvm/x86.c:7067 [inline]
>  vcpu_run arch/x86/kvm/x86.c:7129 [inline]
>  kvm_arch_vcpu_ioctl_run+0x1d53/0x5d20 arch/x86/kvm/x86.c:7299
>  kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2551
>  vfs_ioctl fs/ioctl.c:46 [inline]
>  do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:686
>  SYSC_ioctl fs/ioctl.c:701 [inline]
>  SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
>  entry_SYSCALL_64_fastpath+0x1f/0x96
> RIP: 0033:0x4529d9
> RSP: 002b:00007f15dd481c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 00000000007580d8 RCX: 00000000004529d9
> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000018
> RBP: 000000000000004f R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006ed808
> R13: 00000000ffffffff R14: 00007f15dd4826d4 R15: 0000000000000002
> Code: 43 24 00 00 00 00 48 83 e7 f8 48 29 fb 8d 4b 2c c1 e9 03 f3 48 ab 48
> 81 c4 c0 01 00 00 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <cc> 1f 44 00 00
> 65 8b 05 c4 a5 b4 7e 89 c0 48 0f a3 05 ca 31 12
> RIP: try_to_wake_up+0x140/0x1600 kernel/sched/core.c:2086 RSP:
> ffff8801db407740
> CR2: fffffffffffffff8
> ---[ end trace 4b9063662f5ef94e ]---

#syz dup: BUG: unable to handle kernel paging request in __switch_to

> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@...glegroups.com.
> Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>
>
> 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 in the email body.
>
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bugs+unsubscribe@...glegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a11425c9424da95055f706539%40google.com.
> For more options, visit https://groups.google.com/d/optout.