From: syzbot <syzbot+f2ca20d4aa1408b0385a@syzkaller.appspotmail.com>
To: alexander.deucher@amd.com, bigeasy@linutronix.de, bp@alien8.de,
dave.hansen@intel.com, dvyukov@google.com, hpa@zytor.com,
linmiaohe@huawei.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, nicholas.kazlauskas@amd.com,
pbonzini@redhat.com, riel@surriel.com,
sean.j.christopherson@intel.com, sunpeng.li@amd.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org, zhan.liu@amd.com
Subject: Re: WARNING in switch_fpu_return
Date: Sun, 22 Mar 2020 15:41:03 -0700 [thread overview]
Message-ID: <000000000000ac36ba05a1793693@google.com> (raw)
In-Reply-To: <000000000000f04e43059b1ee697@google.com>
syzbot suspects this bug was fixed by commit:
commit 3009afc6e39e78708d8fb444ae50544b3bcd3a3f
Author: Sean Christopherson <sean.j.christopherson@intel.com>
Date: Wed Jan 22 04:43:39 2020 +0000
KVM: x86: Use a typedef for fastop functions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1667aa4be00000
start commit: bf8d1cd4 Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35
dashboard link: https://syzkaller.appspot.com/bug?extid=f2ca20d4aa1408b0385a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=151d549ee00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: KVM: x86: Use a typedef for fastop functions
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-22 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 2:25 WARNING in switch_fpu_return syzbot
2020-01-07 20:53 ` Sebastian Andrzej Siewior
2020-01-08 4:28 ` Dmitry Vyukov
2020-01-08 8:55 ` Sebastian Andrzej Siewior
2020-01-08 9:03 ` Dmitry Vyukov
2020-03-22 22:41 ` syzbot [this message]
2020-03-23 15:01 ` Sean Christopherson
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=000000000000ac36ba05a1793693@google.com \
--to=syzbot+f2ca20d4aa1408b0385a@syzkaller.appspotmail.com \
--cc=alexander.deucher@amd.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=sean.j.christopherson@intel.com \
--cc=sunpeng.li@amd.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhan.liu@amd.com \
/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.