From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+05017ad275a64a3246f8@syzkaller.appspotmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com, bhelgaas@google.com,
bp@alien8.de, dave.hansen@linux.intel.com,
devel@driverdev.osuosl.org, f.fainelli@gmail.com,
gregkh@linuxfoundation.org, hpa@zytor.com,
info@cestasdeplastico.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-pci@vger.kernel.org,
linux-rpi-kernel-owner@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com,
mchehab@kernel.org, mingo@redhat.com, nsaenzjulienne@suse.de,
pbonzini@redhat.com, robh@kernel.org,
sean.j.christopherson@intel.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, tcs_kernel@tencent.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org
Subject: Re: [syzbot] BUG: spinlock bad magic in synchronize_srcu
Date: Thu, 28 Oct 2021 14:58:13 +0000 [thread overview]
Message-ID: <YXq6hTAOhOaWGsNA@google.com> (raw)
In-Reply-To: <000000000000792dda05cf604775@google.com>
On Wed, Oct 27, 2021, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit eb7511bf9182292ef1df1082d23039e856d1ddfb
> Author: Haimin Zhang <tcs_kernel@tencent.com>
> Date: Fri Sep 3 02:37:06 2021 +0000
>
> KVM: x86: Handle SRCU initialization failure during page track init
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=143e2b02b00000
> start commit: 78e709522d2c Merge tag 'for_linus' of git://git.kernel.org..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=2150ebd7e72fa695
> dashboard link: https://syzkaller.appspot.com/bug?extid=05017ad275a64a3246f8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b72895300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c42853300000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: KVM: x86: Handle SRCU initialization failure during page track init
#syz fix: KVM: x86: Handle SRCU initialization failure during page track init
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+05017ad275a64a3246f8@syzkaller.appspotmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com, bhelgaas@google.com,
bp@alien8.de, dave.hansen@linux.intel.com,
devel@driverdev.osuosl.org, f.fainelli@gmail.com,
gregkh@linuxfoundation.org, hpa@zytor.com,
info@cestasdeplastico.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-pci@vger.kernel.org,
linux-rpi-kernel-owner@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com,
mchehab@kernel.org, mingo@redhat.com, nsaenzjulienne@suse.de,
pbonzini@redhat.com, robh@kernel.org,
sean.j.christopherson@intel.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, tcs_kernel@tencent.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org
Subject: Re: [syzbot] BUG: spinlock bad magic in synchronize_srcu
Date: Thu, 28 Oct 2021 14:58:13 +0000 [thread overview]
Message-ID: <YXq6hTAOhOaWGsNA@google.com> (raw)
In-Reply-To: <000000000000792dda05cf604775@google.com>
On Wed, Oct 27, 2021, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit eb7511bf9182292ef1df1082d23039e856d1ddfb
> Author: Haimin Zhang <tcs_kernel@tencent.com>
> Date: Fri Sep 3 02:37:06 2021 +0000
>
> KVM: x86: Handle SRCU initialization failure during page track init
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=143e2b02b00000
> start commit: 78e709522d2c Merge tag 'for_linus' of git://git.kernel.org..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=2150ebd7e72fa695
> dashboard link: https://syzkaller.appspot.com/bug?extid=05017ad275a64a3246f8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b72895300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c42853300000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: KVM: x86: Handle SRCU initialization failure during page track init
#syz fix: KVM: x86: Handle SRCU initialization failure during page track init
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-28 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 19:02 BUG: spinlock bad magic in synchronize_srcu syzbot
2020-09-26 18:51 ` syzbot
2021-09-12 20:45 ` [syzbot] " syzbot
2021-09-12 20:45 ` syzbot
2021-10-28 2:15 ` syzbot
2021-10-28 2:15 ` syzbot
2021-10-28 14:58 ` Sean Christopherson [this message]
2021-10-28 14:58 ` 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=YXq6hTAOhOaWGsNA@google.com \
--to=seanjc@google.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=info@cestasdeplastico.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel-owner@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=nsaenzjulienne@suse.de \
--cc=pbonzini@redhat.com \
--cc=robh@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+05017ad275a64a3246f8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tcs_kernel@tencent.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 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.