[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqF9VEBah+vvCtoR@mit.edu>
Date: Thu, 9 Jun 2022 00:55:48 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Jason Wang <jasowang@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
Marc Zyngier <maz@...nel.org>,
Halil Pasic <pasic@...ux.ibm.com>,
Cornelia Huck <cohuck@...hat.com>,
Vineeth Vijayan <vneethv@...ux.ibm.com>,
Peter Oberparleiter <oberpar@...ux.ibm.com>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
horsten Leemhuis <regressions@...mhuis.info>
Subject: REGRESSION 5.19-rc1: virtio: harden vring IRQ
I can no longer boot v5.19-rc1 on a Google Compute Engine VM. This
bisected to commit 8b4ec69d7e09 ("virtio: harden vring IRQ"). Its
parent commit, be83f04d2529 ("virtio: allow to unbreak virtqueue")
does successfully boot, so it appears to be caused by commit
8b4ec69d7e09.
I've attached the console log and the config file which I used (which
was generated by using "kvm-xfstests install-kconfig"[1] which is
essentially a "make olddefconfig" of [2]
[1] https://github.com/tytso/xfstests-bld/blob/master/kernel-build/install-kconfig
[2] https://github.com/tytso/xfstests-bld/blob/master/kernel-build/kernel-configs/x86_64-config-5.15
Unfortunately, commit 8b4ec69d7e09 doesn't revert cleanly against
v5.19-rc1, but I can look into figure out how to do revert it if
necessary.
Is this a known issue?
Thanks,
- Ted
View attachment "console-fail" of type "text/plain" (25200 bytes)
Download attachment "config.gz" of type "application/gzip" (18967 bytes)
Powered by blists - more mailing lists