linux-kernel - Re: [syzbot] WARNING in x86_emulate

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+CxaJ2Wu-f0Ys-1Fi7mo4FY9YBXNymdt142poSuND-K36A@mail.gmail.com>
Date:   Fri, 28 May 2021 08:34:28 +0800
From:   Wanpeng Li <kernellwp@...il.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        syzbot <syzbot+71271244f206d17f6441@...kaller.appspotmail.com>,
        Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        "H. Peter Anvin" <hpa@...or.com>, jarkko@...nel.org,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>, kan.liang@...ux.intel.com,
        kvm <kvm@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
        linux-sgx@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Sean Christopherson <seanjc@...gle.com>, steve.wahl@....com,
        syzkaller-bugs@...glegroups.com,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [syzbot] WARNING in x86_emulate_instruction

On Fri, 28 May 2021 at 08:31, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Fri, May 28 2021 at 01:21, Paolo Bonzini wrote:
> > On 28/05/21 00:52, Thomas Gleixner wrote:
> >>
> >> So this is stale for a week now. It's fully reproducible and nobody
> >> can't be bothered to look at that?
> >>
> >> What's wrong with you people?
> >
> > Actually there's a patch on list ("KVM: X86: Fix warning caused by stale
> > emulation context").  Take care.
>
> That's useful, but does not change the fact that nobody bothered to
> reply to this report ...

Will do it next time. Have a nice evening, guys!