From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: [PATCH][ACM] kernel enforcement of vbd policies via blkback driver Date: Thu, 27 Jul 2006 18:19:17 +0100 Message-ID: <1154020758.7906.46.camel@localhost.localdomain> References: <1154020010.7906.44.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1154020010.7906.44.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Reiner Sailer Cc: Andrew Warfield , xen-devel@lists.xensource.com, xense-devel@lists.xensource.com, Bryan D Payne , ncmike@us.ibm.com List-Id: xen-devel@lists.xenproject.org On Thu, 2006-07-27 at 18:06 +0100, Harry Butterworth wrote: > Even with local devices there is no security on the device side of the > device driver. Consider the case of a locally attached sata drive > containing 2 partitions, one for each of two domains. It's not unheard > of for disk drives to write the data in the wrong place. Or read and > return the wrong block. Happens all the time. And there's all that unaudited code in the motherboard RAID implementation. What's to say that isn't going to shuffle your data between partitions?