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

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANRm+Cy_=ZO9eJGk2HzgN0by_c_uoEPFNa850+GvsYvJAw0DwA@mail.gmail.com>
Date:   Fri, 15 Dec 2017 17:58:41 +0800
From:   Wanpeng Li <kernellwp@...il.com>
To:     David Hildenbrand <david@...hat.com>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andy Lutomirski <luto@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        syzbot 
        <bot+1f445b1009b8eeededa30fe62ccf685f2ec9d155@...kaller.appspotmail.com>,
        Borislav Petkov <bp@...e.de>,
        Dmitry Safonov <dsafonov@...tuozzo.com>,
        Peter Anvin <hpa@...or.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Kyle Huey <me@...ehuey.com>, Ingo Molnar <mingo@...hat.com>,
        syzkaller-bugs@...glegroups.com,
        "the arch/x86 maintainers" <x86@...nel.org>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        KVM list <kvm@...r.kernel.org>,
        "Lan, Tianyu" <tianyu.lan@...el.com>,
        James Mattson <jmattson@...gle.com>
Subject: Re: BUG: unable to handle kernel paging request in __switch_to

2017-12-15 17:51 GMT+08:00 David Hildenbrand <david@...hat.com>:
>
>> int main()
>> {
>>   int fd = open("/dev/kvm", 0x80102ul);
>>   int vm = ioctl(fd, KVM_CREATE_VM, 0);
>>   int  cpu = ioctl(vm, KVM_CREATE_VCPU, 4);
>
> Not even a memory region :) So maybe the first memory access directly
> triggers a fault?
>
>>   ioctl(cpu, KVM_RUN, 0);
>>   return 0;
>> }
>>
>> And, yes, this in fact triggers instant reboot of kernel (running in qemu).
>> Am I missing something here?
>>
>> +kvm maintainers, you can see full thread here:
>> https://groups.google.com/forum/#!topic/syzkaller-bugs/_oveOKGm3jw

I didn't see any issue after running the test.

Regards,
Wanpeng Li