linux-kernel - Re: REGRESSION 5.19-rc1: virtio: harden vring IRQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 9 Jun 2022 14:19:59 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     "Theodore Ts'o" <tytso@....edu>
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 <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        horsten Leemhuis <regressions@...mhuis.info>
Subject: Re: REGRESSION 5.19-rc1: virtio: harden vring IRQ

Hi:

On Thu, Jun 9, 2022 at 12:57 PM Theodore Ts'o <tytso@....edu> wrote:
>
> 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?

This seems to be the same issue as the syzbot report recently.

Would you please test this patch to see if it works?

https://www.spinics.net/lists/kernel/msg4389357.html

Thanks

>
> Thanks,
>
>                                                 - Ted
>