From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+579eb95e588b48b4499c@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [kvm?] KMSAN: uninit-value in em_ret_far
Date: Fri, 9 Feb 2024 13:10:03 -0800 [thread overview]
Message-ID: <ZcaUq68756CcW74y@google.com> (raw)
In-Reply-To: <0000000000009c91ce060e87575b@google.com>
On Tue, Jan 09, 2024, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 2cf4f94d8e86 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=144e8d01e80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4a65fa9f077ead01
> dashboard link: https://syzkaller.appspot.com/bug?extid=579eb95e588b48b4499c
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/589557edbfd5/disk-2cf4f94d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f2480533f00e/vmlinux-2cf4f94d.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/9463e8eac2ed/bzImage-2cf4f94d.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+579eb95e588b48b4499c@syzkaller.appspotmail.com
#syz fix: KVM: x86: Clean up partially uninitialized integer in emulate_pop()
next prev parent reply other threads:[~2024-02-09 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 18:18 [syzbot] [kvm?] KMSAN: uninit-value in em_ret_far syzbot
2024-01-19 15:56 ` [syzbot] " syzbot
2024-01-22 8:20 ` syzbot
2024-02-09 21:10 ` Sean Christopherson [this message]
[not found] <20240119155614.4501-1-n.zhandarovich@fintech.ru>
2024-01-19 16:42 ` syzbot
2024-01-19 16:55 ` Aleksandr Nogikh
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=ZcaUq68756CcW74y@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzbot+579eb95e588b48b4499c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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