Re: [Xen-devel] [PATCH v4 03/34] xsm/xen_version: Add XSM for the xen_version hypercall

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

> >diff --git a/xen/xsm/flask/policy/security_classes 
> >b/xen/xsm/flask/policy/security_classes
> >index ca191db..cde4e1a 100644
> >--- a/xen/xsm/flask/policy/security_classes
> >+++ b/xen/xsm/flask/policy/security_classes
> >@@ -18,5 +18,6 @@ class shadow
> >  class event
> >  class grant
> >  class security
> >+class version
> >
> >  # FLASK
> >
> Can we have more meaningful name for XSM class. "version" doesn't seem to be
> informative enough to convey the message as to why we need it to be secure.
> (Is it a resource, or domain specific or event or...)

Heya!

1). Please trim your replies.
2). The patch is already in the tree.
3). If you prefer a different name - by all means please submit a patch for 
that.
    I am all up for it.
> 
> My suggestion would be xenmetainfo or something more meaningful.

/me blinks

Metainfo? I am not sure how one is suppose to associate that with
features that the hypervisor is exposing to guests.

> 
> Anshul
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel