xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Xin Li <xin.li@citrix.com>, Tim Deegan <tim@xen.org>,
	Jan Beulich <JBeulich@suse.com>, Ming Lu <ming.lu@citrix.com>
Subject: Re: [PATCH 2/2] xen/xsm: Rename CONIFIG_XSM_POLICY to CONFIG_XSM_FLASK_POLICY
Date: Sat, 18 Aug 2018 00:40:16 +0100	[thread overview]
Message-ID: <157bae5d-7d0c-e649-f4dd-f4b7cf52dd48@citrix.com> (raw)
In-Reply-To: <3d7fd969-4506-f0bc-1178-579c25d4e547@tycho.nsa.gov>

On 17/08/18 19:57, Daniel De Graaf wrote:
> On 06/26/2018 07:09 AM, Andrew Cooper wrote:
>> The embedded policy is specific flask, so update the infrastructure
>> to reflect
>> this.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> This one actually has a history of being shared between FLASK and ACM
> (the
> now-removed alternative to FLASK in earlier versions of Xen). 
> However, the
> current policy generation is very specific to FLASK, and it would be
> useful
> to allow multiple security modules to each have their own default policy.
>
> Overall, I think it's a useful change.  Is there a reason you chose the
> prefix "xsm_init_flask" over "xsm_flask_init"?  The latter may be more
> amenable to grepping.
>
> Either way,
>
> Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>

This was some sed to begin with, which is why they ended up like that. 
I will make those adjustments.

Thanks,

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-08-17 23:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 11:09 [PATCH 0/2] xen/xsm: Cleanup in preparation for XSM SILO mode Andrew Cooper
2018-06-26 11:09 ` [PATCH 1/2] xen/xsm: Rename CONFIG_FLASK_* to CONFIG_XSM_FLASK_* Andrew Cooper
2018-06-27 21:21   ` Doug Goldstein
2018-08-17 18:49   ` Daniel De Graaf
2018-06-26 11:09 ` [PATCH 2/2] xen/xsm: Rename CONIFIG_XSM_POLICY to CONFIG_XSM_FLASK_POLICY Andrew Cooper
2018-06-27 21:24   ` [PATCH 2/2] xen/xsm: Rename CONFIG_XSM_POLICY " Doug Goldstein
2018-08-17 18:57   ` [PATCH 2/2] xen/xsm: Rename CONIFIG_XSM_POLICY " Daniel De Graaf
2018-08-17 23:40     ` Andrew Cooper [this message]
2018-06-26 12:04 ` [PATCH 0/2] xen/xsm: Cleanup in preparation for XSM SILO mode Jan Beulich
2018-06-26 12:42   ` Andrew Cooper
2018-06-26 13:16     ` Jan Beulich
2018-06-27 21:19       ` Doug Goldstein
2018-06-27 23:06       ` Andrew Cooper
2018-08-16 12:46 ` Andrew Cooper
2018-08-16 12:56   ` Jan Beulich
2018-08-16 13:18     ` Andrew Cooper
2018-08-16 13:46       ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=157bae5d-7d0c-e649-f4dd-f4b7cf52dd48@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ming.lu@citrix.com \
    --cc=sergey.dyasli@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xin.li@citrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).