From: Paolo Bonzini <pbonzini@redhat.com>
To: syzbot <syzbot+9a89b866d3fc11acc3b6@syzkaller.appspotmail.com>,
bp@alien8.de, hpa@zytor.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
seanjc@google.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org
Subject: Re: [syzbot] possible deadlock in kvm_synchronize_tsc
Date: Wed, 24 Mar 2021 13:17:00 +0100 [thread overview]
Message-ID: <dd9de982-e94d-163f-067b-d86d95e947a8@redhat.com> (raw)
In-Reply-To: <00000000000099aa6805be432fce@google.com>
On 24/03/21 08:24, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 1c273e10 Merge tag 'zonefs-5.12-rc4' of git://git.kernel.o..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1063d14ed00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=6abda3336c698a07
> dashboard link: https://syzkaller.appspot.com/bug?extid=9a89b866d3fc11acc3b6
> userspace arch: i386
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10bf56f6d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=174e36dcd00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+9a89b866d3fc11acc3b6@syzkaller.appspotmail.com
#syz dup: possible deadlock in scheduler_tick
prev parent reply other threads:[~2021-03-24 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 7:24 [syzbot] possible deadlock in kvm_synchronize_tsc syzbot
2021-03-24 12:17 ` 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=dd9de982-e94d-163f-067b-d86d95e947a8@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=syzbot+9a89b866d3fc11acc3b6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@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).