linux-kernel - Re: [Xen-devel] [PATCH] xen: Remove event channel notification through Xen PCI platform device

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]

Message-ID: <57EE7AB7.4020405@citrix.com>
Date:   Fri, 30 Sep 2016 15:46:15 +0100
From:   David Vrabel <david.vrabel@...rix.com>
To:     KarimAllah Ahmed <karahmed@...zon.de>,
        <linux-kernel@...r.kernel.org>, <xen-devel@...ts.xenproject.org>
CC:     Juergen Gross <jgross@...e.com>,
        Ross Lagerwall <ross.lagerwall@...rix.com>,
        <linux-pci@...r.kernel.org>, <x86@...nel.org>,
        Paul Gortmaker <paul.gortmaker@...driver.com>,
        Julien Grall <julien.grall@...rix.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        "Ingo Molnar" <mingo@...hat.com>,
        David Vrabel <david.vrabel@...rix.com>,
        "Anthony Liguori" <aliguori@...zon.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        "Bjorn Helgaas" <bhelgaas@...gle.com>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Stefano Stabellini <stefano.stabellini@...citrix.com>
Subject: Re: [Xen-devel] [PATCH] xen: Remove event channel notification
 through Xen PCI platform device

On 26/08/16 22:55, KarimAllah Ahmed wrote:
> Ever since commit 254d1a3f02eb ("xen/pv-on-hvm kexec: shutdown watches
> from old kernel") using the INTx interrupt from Xen PCI platform device for
> event channel notification would just lockup the guest during bootup.
> postcore_initcall now calls xs_reset_watches which will eventually try to read
> a value from XenStore and will get stuck on read_reply at XenBus forever since
> the platform driver is not probed yet and its INTx interrupt handler is not
> registered yet. That means that the guest can not be notified at this moment of
> any pending event channels and none of the per-event handlers will ever be
> invoked (including the XenStore one) and the reply will never be picked up by
> the kernel.

Applied to for-linus-4.9, thanks.

David