From: syzbot <syzbot+0c6da80218456f1edc36@syzkaller•appspotmail.com>
To: akpm@linux-foundation•org, davem@davemloft•net, jhs@mojatatu•com,
jiri@resnulli•us, kvm@vger•kernel.org,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
mingo@elte•hu, mlevitsk@redhat•com, netdev@vger•kernel.org,
pbonzini@redhat•com, peterz@infradead•org, seanjc@google•com,
syzkaller-bugs@googlegroups•com, tglx@linutronix•de,
vinicius.gomes@intel•com, viro@zeniv•linux.org.uk,
xiyou.wangcong@gmail•com
Subject: Re: [syzbot] INFO: task hung in synchronize_rcu (3)
Date: Tue, 10 May 2022 01:51:13 -0700 [thread overview]
Message-ID: <0000000000004f3c0d05dea46dac@google.com> (raw)
In-Reply-To: <000000000000402c5305ab0bd2a2@google.com>
syzbot suspects this issue was fixed by commit:
commit 2d08935682ac5f6bfb70f7e6844ec27d4a245fa4
Author: Sean Christopherson <seanjc@google•com>
Date: Fri Apr 15 00:43:41 2022 +0000
KVM: x86: Don't re-acquire SRCU lock in complete_emulated_io()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16dc2e49f00000
start commit: ea4424be1688 Merge tag 'mtd/fixes-for-5.17-rc8' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=442f8ac61e60a75e
dashboard link: https://syzkaller.appspot.com/bug?extid=0c6da80218456f1edc36
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1685af9e700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b09df1700000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: KVM: x86: Don't re-acquire SRCU lock in complete_emulated_io()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-05-10 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000402c5305ab0bd2a2@google.com>
2020-07-25 5:11 ` INFO: task hung in synchronize_rcu (3) syzbot
2022-05-10 8:51 ` syzbot [this message]
2022-05-10 13:45 ` [syzbot] " Sean Christopherson
2022-05-10 13:50 ` Paolo Bonzini
2022-05-10 13:56 ` 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=0000000000004f3c0d05dea46dac@google.com \
--to=syzbot+0c6da80218456f1edc36@syzkaller$(echo .)appspotmail.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=mlevitsk@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=seanjc@google$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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