On 6/20/16 9:04 AM, Daniel De Graaf wrote:
> Since enabling XSM is required to enable FLASK, place the option for
> FLASK below the one for XSM.  In addition, since it does not make sense
> to enable XSM without any XSM providers, and FLASK is the only XSM
> provider, hide the option to disable FLASK under EXPERT.
> 
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> ---
>  xen/common/Kconfig | 37 +++++++++++++++++++------------------
>  1 file changed, 19 insertions(+), 18 deletions(-)
> 
> diff --git a/xen/common/Kconfig b/xen/common/Kconfig
> index cd59574..6a51fd5 100644
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -11,24 +11,6 @@ config COMPAT
>  config CORE_PARKING
>  	bool
>  
> -config FLASK
> -	bool "FLux Advanced Security Kernel support"
> -	default y
> -	depends on XSM
> -	---help---
> -	  Enables the FLASK (FLux Advanced Security Kernel) support which
> -	  provides a mandatory access control framework by which security
> -	  enforcement, isolation, and auditing can be achieved with fine
> -	  granular control via a security policy.
> -
> -	  If unsure, say N.
> -

<snip>

>  
> +config FLASK
> +	def_bool y
> +	bool "FLux Advanced Security Kernel support" if EXPERT = "y"

Why did FLASK become dependent on EXPERT? It wasn't previously.

-- 
Doug Goldstein