[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] ACM ternary ops?



Hello all,

I am interested in adding support for user-defined mandatory network access control policies to the existing ACM policy framework. The most logical way to do this would be to add more hooks to handle networking and then define another policy module, like chinese wall and type enforcement. However, it doesn't feel right to add a "ternary_ops" structure that is invoked after "secondary_ops". Is there any reasonable justification for not including a link in each ops structure that points to the next policy module in the chain? Essentially, I'd like to convert the current n-pointer structure to the following linked-list structure:

acm_primary_ops -> acm_secondary_ops -> acm_ternary_ops -> ... -> NULL


Thanks.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.