Re: secilc: in statement ordering limitations

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

 



On 05/23/2014 11:04 AM, Steve Lawrence wrote:
On 05/23/2014 10:32 AM, Dominick Grift wrote:
On Fri, 2014-05-23 at 09:15 -0400, James Carter wrote:

Could you give me a little bit more information on what you are doing?

Strange.. It is kind of hard for me to put it any other way.

I have a short 5 minute video that demo's the issue:

https://www.youtube.com/watch?v=hU_yVZJpAyM

If you are not able to view the demo then i guess i will have to find
another way to explain it


I think this is an example of the core problem:

   (in foo.bar
     (type x))

   (in foo
     (block bar))

   (block foo)

So, an in-statement is inserting into a block that is created by another
in-statement, so there's an order dependence.


So to fix this we need to split up the processing for "in", so that blocks and macros are processed first?

Jim

--
James Carter <jwcart2@xxxxxxxxxxxxx>
National Security Agency
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.




[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux