[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] bug suspcion and proposed modification when xen-pciback failed to map an irq (-19) to a domU


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: "DOZ, MARC (ext)" <marc.doz.external@xxxxxxxx>
  • Date: Fri, 29 Nov 2019 12:34:49 +0000
  • Accept-language: fr-FR, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=atos.net; dmarc=pass action=none header.from=atos.net; dkim=pass header.d=atos.net; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xi8yCC+7YLK2B4D5Jx3LlINVbRf+QLKoekaOHMI2HRw=; b=QZms5UiOmCu6Dphb4JktTlMQUAkozbkxzfEdYZJcac0Gg3Ypt6V8yf0H6ftwZy83Rwl9G1RD4rIfK962F1TkdTdaymr8ftFUion2CZssLewHPMaJk6o/i9RC41pIaLonbO/w29X3p0TPUivvmmwUFFGqbA7YPf8iv+I58y9GQjNgf2zFX219c1FuV94PBBqMvJKmOiJE3XvMQHkXcHglQCIBOG16Hrk3smaAtM8R3iC1Ah5v6NzcgIjLDFO0SLlWDbfN6NZzreZ2K9adP/0HDmGpkZoDg28d5xGqkKs+fs9b773fYfwXnMFaTgK9X/dgFSUr/ozFANwY9cwmhfm9yg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G4ewymhTmPbMkdqGu7rwrNwDNBAwziJ4Vzh5e+5YjYPYUIC/qVthuxiPsaNbXtr+npC7rk9voYcWtS6hTtxtGuRoYq7BK2ZWWHlOhup2XPN1/NsOAJ+kfw1jyWvcBsb7XBy7rgmSDCJ7veCa5X/IYhwEog7gjgNwhGPovCs2nf5LS3qAjgzUbhOD8ji8LMWObKsAl8SX1rAxBPbFlnlIkLIdnxuPEYb/X7Z46PWn6LSSdztlQmmrG7u7qYiqx0bJKxpzYz6GVg0thIiplf3z6EfmtGjidG2alzCCjkzrxGYL53sYAnx8RnYgurEPmDr97ZcbPOAlGa6TJ4NFgKwXuQ==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=marc.doz.external@xxxxxxxx;
  • Delivery-date: Fri, 29 Nov 2019 12:35:42 +0000
  • Ironport-sdr: y2T5GDQbBIhO8lKn0NyZR4gqmook3auleQOvqMvsPe8CdTy+JAOswAc2shbg60jRMT5eq5zwUC +ZbX1j2nIKy6O1znlAXCEwkj1zEUduVy7Qq0H8QtCWcp1V/ZLiEMwya9Ey8n8Hdb5M7weUYkgK Fsws7XzGvpes1DFb3PxB7kpLkmTFVx90UlIv5wj/oG6ut0biTB1Nh9gvHTVvAWk3KXrX92cNB7 WE4lwSNggcCCg30IbZuXF8LbLWst+PolHDPriWAe9krggpg/1M7MKR1yuBLVUYFeBKT9fUeok6 6VPwlDIZjq1FsgVVUja3WESv
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AdWmkKtK1mIfCnPYTFqu2ZiOwgqUvwAEPQGAAAOYXhA=
  • Thread-topic: [Xen-devel] bug suspcion and proposed modification when xen-pciback failed to map an irq (-19) to a domU

>Except that this is not a "fix", but the introduction of a security 
>vulnerability (permitting interrupt setup on un-owned devices). See XSA-237, 
>which actually changed it in the opposite direction of what you're proposing.

Ok, I found it :
https://xenbits.xen.org/xsa/xsa237-4.5/0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch

"MSI setup should be permitted only for existing devices owned by the 
respective guest" 

But how to change the owner of my device or update the pdev->domain->domain_id ?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.