From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>,
Wanpeng Li <kernellwp@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
syzkaller <syzkaller@googlegroups.com>
Cc: syzbot <syzbot+71271244f206d17f6441@syzkaller.appspotmail.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
jarkko@kernel.org, Jim Mattson <jmattson@google.com>,
Joerg Roedel <joro@8bytes.org>,
kan.liang@linux.intel.com, kvm <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-sgx@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
steve.wahl@hpe.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [syzbot] WARNING in x86_emulate_instruction
Date: Mon, 7 Jun 2021 15:58:19 +0200 [thread overview]
Message-ID: <fa3c04ea-f27f-eeb2-d118-77f8fb805a8a@redhat.com> (raw)
In-Reply-To: <CACT4Y+YDtBf1GebeAA=twsfuv9e0HN+w7Lt5ZqDJhMJ5-PWYXQ@mail.gmail.com>
On 07/06/21 12:34, Dmitry Vyukov wrote:
> On Fri, May 28, 2021 at 2:34 AM Wanpeng Li <kernellwp@gmail.com> wrote:
>>
>> On Fri, 28 May 2021 at 08:31, Thomas Gleixner <tglx@linutronix.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!
>
> There was an idea to do this automatically by syzbot:
>
> dashboard/app: notify bug report about fix patches
> https://github.com/google/syzkaller/issues/1574
>
> Namely: if syzbot discovers a fix anywhere (by the hash), it could
> send a notification email to the bug report email thread.
> The downside is that the robot sends even more emails, so I am not
> sure how it will be accepted. Any opinions?
I would like it. Usually somebody replies _before_ they start working
on it, but sometimes they send a patch right away.
Paolo
prev parent reply other threads:[~2021-06-07 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 2:52 [syzbot] WARNING in x86_emulate_instruction syzbot
2021-05-27 22:52 ` Thomas Gleixner
2021-05-27 23:21 ` Paolo Bonzini
2021-05-27 23:56 ` Thomas Gleixner
2021-05-28 0:34 ` Wanpeng Li
2021-06-07 10:34 ` Dmitry Vyukov
2021-06-07 13:58 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa3c04ea-f27f-eeb2-d118-77f8fb805a8a@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kan.liang@linux.intel.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=steve.wahl@hpe.com \
--cc=syzbot+71271244f206d17f6441@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).