linux-kernel - Re: [PATCH v7 4/4] vfio: convey kvm that the vfio-pci device is wc safe

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: Tue, 13 Feb 2024 01:59:45 +0000
From: Ankit Agrawal <ankita@...dia.com>
To: Alex Williamson <alex.williamson@...hat.com>, Jason Gunthorpe
	<jgg@...dia.com>
CC: "maz@...nel.org" <maz@...nel.org>, "oliver.upton@...ux.dev"
	<oliver.upton@...ux.dev>, "james.morse@....com" <james.morse@....com>,
	"suzuki.poulose@....com" <suzuki.poulose@....com>, "yuzenghui@...wei.com"
	<yuzenghui@...wei.com>, "reinette.chatre@...el.com"
	<reinette.chatre@...el.com>, "surenb@...gle.com" <surenb@...gle.com>,
	"stefanha@...hat.com" <stefanha@...hat.com>, "brauner@...nel.org"
	<brauner@...nel.org>, "catalin.marinas@....com" <catalin.marinas@....com>,
	"will@...nel.org" <will@...nel.org>, "mark.rutland@....com"
	<mark.rutland@....com>, "kevin.tian@...el.com" <kevin.tian@...el.com>,
	"yi.l.liu@...el.com" <yi.l.liu@...el.com>, "ardb@...nel.org"
	<ardb@...nel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"andreyknvl@...il.com" <andreyknvl@...il.com>, "wangjinchao@...sion.com"
	<wangjinchao@...sion.com>, "gshan@...hat.com" <gshan@...hat.com>,
	"shahuang@...hat.com" <shahuang@...hat.com>, "ricarkol@...gle.com"
	<ricarkol@...gle.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
	"lpieralisi@...nel.org" <lpieralisi@...nel.org>, "rananta@...gle.com"
	<rananta@...gle.com>, "ryan.roberts@....com" <ryan.roberts@....com>,
	"david@...hat.com" <david@...hat.com>, "linus.walleij@...aro.org"
	<linus.walleij@...aro.org>, "bhe@...hat.com" <bhe@...hat.com>, Aniket Agashe
	<aniketa@...dia.com>, Neo Jia <cjia@...dia.com>, Kirti Wankhede
	<kwankhede@...dia.com>, "Tarun Gupta (SW-GPU)" <targupta@...dia.com>, Vikram
 Sethi <vsethi@...dia.com>, Andy Currid <acurrid@...dia.com>, Alistair Popple
	<apopple@...dia.com>, John Hubbard <jhubbard@...dia.com>, Dan Williams
	<danw@...dia.com>, "kvmarm@...ts.linux.dev" <kvmarm@...ts.linux.dev>, Matt
 Ochs <mochs@...dia.com>, Zhi Wang <zhiw@...dia.com>, "kvm@...r.kernel.org"
	<kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v7 4/4] vfio: convey kvm that the vfio-pci device is wc
 safe

>>   IP requires platform integration to take responsibility to prevent
>>   this.
>>
>>   To safely use VFIO in KVM the platform must guarantee full safety
>>   in the guest where no action taken against a MMIO mapping can
>>   trigger an uncontainer failure. We belive that most VFIO PCI
>>   platforms support this for both mapping types, at least in common
>>   flows, based on some expectations of how PCI IP is integrated. This
>>   can be enabled more broadly, for instance into vfio-platform
>>   drivers, but only after the platform vendor completes auditing for
>>   safety.
>
> I like it, please incorporate into the next version.

Yes, will fix the typos and add it.