WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: xsm: Consolidate xsm processing within domain control hy

To: "George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: xsm: Consolidate xsm processing within domain control hypercall.
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Tue, 4 Dec 2007 16:59:02 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 04 Dec 2007 13:59:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C37B36C2.10B43%gscoker@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <20071204214635.GB23369@xxxxxxxxxxxxxxxxxxxxxx> <C37B36C2.10B43%gscoker@xxxxxxxxxxxxxx>
Reply-to: ncmike@xxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.15+20070412 (2007-04-11)
On 04/12/07 16:54 -0500, George S. Coker, II wrote:
> 
> > 
> >> 2) This will also impose on the security modules the responsibility to
> >> acquire and hold locks on hypervisor resources.  It would seem dangerous to
> >> give modules this responsibility.
> > 
> > I don't see it, the locking logic is still the same. Can you show me
> > where the module needs to acquire locks differently than without the
> > patch?
> > 
> It's not that the locking logic is different.  A security module may be
> sloppy about its locking and cause Xen to crash without specifically
> indicating a flaw in the security module.
> 
> Getting locks right is tricky business, it would seem the Xen would want the
> responsibility for the locking of resources to avoid the ills of race
> conditions, etc.

I agree with your comments, but I don't think the patch changes
locking at all. If I'm wrong I agree that's a problem. 

Mike

-- 
Mike D. Day
IBM LTC
Cell: 919 412-3900
Sametime: ncmike@xxxxxxxxxx AIM: ncmikeday  Yahoo: ultra.runner
PGP key: http://www.ncultra.org/ncmike/pubkey.asc

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>