1Call / Macro Statements 2======================= 3 4call 5---- 6 7Instantiate a [macro](#macro) within the current namespace. There may be zero or more parameters passed to the macro (with zero parameters this is similar to the [`blockinherit`](cil_container_statements.md#blockinherit) ([`call`](cil_call_macro_statements.md#call)) / [`blockabstract`](cil_container_statements.md#blockabstract) ([`macro`](cil_call_macro_statements.md#macro)) statements). 8 9Each parameter passed contains an argument to be resolved by the [macro](#macro), these can be named or anonymous but must conform to the parameter types defined in the [`macro`](cil_call_macro_statements.md#macro) statement. 10 11Macro rules are resolved by searching in the following order: 12 13- The macro namespace (If found this means that the name was declared in the macro and is now declared in the namespace of one of the parents of the call.) 14 15- The call arguments 16 17- The parent namespaces of the macro being called (if any) with the exception of the global namespace. 18 19- The parent namespaces of the call (if any) with the exception of the global namespace. 20 21- The global namespace 22 23**Statement definition:** 24 25```secil 26 (call macro_id [(param ...)]) 27``` 28 29**Where:** 30 31<table> 32<colgroup> 33<col width="25%" /> 34<col width="75%" /> 35</colgroup> 36<tbody> 37<tr class="odd"> 38<td align="left"><p><code>call</code></p></td> 39<td align="left"><p>The <code>call</code> keyword.</p></td> 40</tr> 41<tr class="even"> 42<td align="left"><p><code>macro_id</code></p></td> 43<td align="left"><p>The identifier of the <code>macro</code> to be instantiated.</p></td> 44</tr> 45<tr class="odd"> 46<td align="left"><p><code>param</code></p></td> 47<td align="left"><p>Zero or more parameters that are passed to the macro.</p></td> 48</tr> 49</tbody> 50</table> 51 52**Example:** 53 54See the [`macro`](cil_call_macro_statements.md#macro) statement for an example. 55 56macro 57----- 58 59Declare a macro in the current namespace with its associated parameters. The macro identifier is used by the [`call`](cil_call_macro_statements.md#call) statement to instantiate the macro and resolve any parameters. The call statement may be within the body of a macro. 60 61[`tunable`](cil_conditional_statements.md#tunable), [`in`](cil_container_statements.md#in), [`block`](cil_container_statements.md#block), [`blockinherit`](cil_container_statements.md#blockinherit), [`blockabstract`](cil_container_statements.md#blockabstract), and other [`macro`](cil_call_macro_statements.md#macro) statements are not allowed in [`macro`](cil_call_macro_statements.md#macro) blocks. 62 63Duplicate [`macro`](cil_call_macro_statements.md#macro) declarations in the same namespace will normally cause an error, but inheriting a macro into a namespace (with [`blockinherit`](cil_container_statements.md#blockinherit)) that already has a macro with the same name will only result in a warning message and not cause an error. This behavior allows inherited macros to be overridden with local ones. 64 65**Statement definition:** 66 67```secil 68 (macro macro_id ([(param_type param_id) ...]) 69 cil_statements 70 ... 71 ) 72``` 73 74**Where:** 75 76<table> 77<colgroup> 78<col width="25%" /> 79<col width="75%" /> 80</colgroup> 81<tbody> 82<tr class="odd"> 83<td align="left"><p><code>macro</code></p></td> 84<td align="left"><p>The <code>macro</code> keyword.</p></td> 85</tr> 86<tr class="even"> 87<td align="left"><p><code>macro_id</code></p></td> 88<td align="left"><p>The <code>macro</code> identifier.</p></td> 89</tr> 90<tr class="odd"> 91<td align="left"><p><code>param_type</code></p></td> 92<td align="left"><p>Zero or more parameters that are passed to the macro. The <code>param_type</code> is a keyword used to determine the declaration type (e.g. <code>type</code>, <code>class</code>, <code>categoryset</code>).</p> 93<p>The list of valid <code>param_type</code> entries are: <code>type</code>, <code>typealias</code>, <code>role</code>, <code>user</code>, <code>sensitivity</code>, <code>sensitivityalias</code>, <code>category</code>, <code>categoryalias</code>, <code>categoryset</code> (named or anonymous), <code>level</code> (named or anonymous), <code>levelrange</code> (named or anonymous), <code>class</code>, <code>classpermission</code> (named or anonymous), <code>ipaddr</code> (named or anonymous), <code>name</code> (a string), <code>classmap</code></p></td> 94</tr> 95<tr class="even"> 96<td align="left"><p><code>param_id</code></p></td> 97<td align="left"><p>The parameter identifier used to reference the entry within the macro body (e.g. <code>ARG1</code>).</p></td> 98</tr> 99<tr class="odd"> 100<td align="left"><p><code>cil_statement</code></p></td> 101<td align="left"><p>Zero or more valid CIL statements.</p></td> 102</tr> 103</tbody> 104</table> 105 106**Examples:** 107 108This example will instantiate the `binder_call` macro in the calling namespace (`my_domain`) and replace `ARG1` with `appdomain` and `ARG2` with `binderservicedomain`: 109 110```secil 111 (block my_domain 112 (call binder_call (appdomain binderservicedomain)) 113 ) 114 115 (macro binder_call ((type ARG1) (type ARG2)) 116 (allow ARG1 ARG2 (binder (call transfer))) 117 (allow ARG2 ARG1 (binder (transfer))) 118 (allow ARG1 ARG2 (fd (use))) 119 ) 120``` 121 122This example does not pass any parameters to the macro but adds a [`type`](cil_type_statements.md#type) identifier to the current namespace: 123 124```secil 125 (block unconfined 126 (call add_type) 127 .... 128 129 (macro add_type () 130 (type exec) 131 ) 132 ) 133``` 134 135This example passes an anonymous and named IP address to the macro: 136 137```secil 138 (ipaddr netmask_1 255.255.255.0) 139 (context netlabel_1 (system.user object_r unconfined.object low_low)) 140 141 (call build_nodecon ((192.168.1.64) netmask_1)) 142 143 (macro build_nodecon ((ipaddr ARG1) (ipaddr ARG2)) 144 (nodecon ARG1 ARG2 netlabel_1) 145 ) 146``` 147