Thread (17 messages) 17 messages, 5 authors, 2019-02-11

Re: [Qemu-devel] security implications of caching with virtio pmem (was Re: [PATCH v3 0/5] kvm "virtio pmem" device)

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2019-02-11 23:07:23
Also in: kvm, linux-acpi, linux-fsdevel, linux-xfs, lkml, nvdimm, qemu-devel

On Mon, Feb 11, 2019 at 11:58:15PM +0100, David Hildenbrand wrote:
On 11.02.19 23:29, Dave Chinner wrote:
quoted
On Mon, Feb 11, 2019 at 02:29:46AM -0500, Pankaj Gupta wrote:
quoted
Hello Dave,
Are we okay with this?
Sure.

I'm not sure I agree with all the analysis presented, but, well, I
haven't looked any deeper because I'm tired of being shouted at and
being called argumentative for daring to ask hard questions about
this topic....
I think if you have concerns, they should definitely be discussed.
Making people frustrated that review code is not what we want. Not at all.

I suggest that Pankaj properly documents what we found out so far about
security concerns and properly describes intended use cases and answers
other questions you had in the cover letter / documentation of the
follow up series.

Thanks Dave!
Right. Also, there's an open question that you posed:
	Also other storage devices have caches like that (well, the caches size
	depends on the device) - thinking especially about storage systems -
	which would in my opinion, also allow similar leaks. How are such
	security concerns handled there? Are they different (besides eventually
	access speed)?
and that needs some looking into, and reporting on.

quoted
Cheers,

Dave.

-- 

Thanks,

David / dhildenb
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help