From: Thomas Gleixner <tglx@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
syzbot <syzbot+71271244f206d17f6441@syzkaller.appspotmail.com>,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
jarkko@kernel.org, jmattson@google.com, joro@8bytes.org,
kan.liang@linux.intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org, seanjc@google.com,
steve.wahl@hpe.com, syzkaller-bugs@googlegroups.com,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] WARNING in x86_emulate_instruction
Date: Fri, 28 May 2021 01:56:06 +0200 [thread overview]
Message-ID: <87sg277muh.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <0f6e6423-f93a-5d96-f452-4e08dbad9b23@redhat.com>
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 ...
next prev parent reply other threads:[~2021-05-27 23:56 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 [this message]
2021-05-28 0:34 ` Wanpeng Li
2021-06-07 10:34 ` Dmitry Vyukov
2021-06-07 13:58 ` Paolo Bonzini
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=87sg277muh.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kan.liang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.