All of lore.kernel.org
 help / color / mirror / Atom feed
* cilc: name space inconsistency
@ 2014-10-17 13:15 Dominick Grift
  2014-10-20 13:34 ` Dominick Grift
  0 siblings, 1 reply; 2+ messages in thread
From: Dominick Grift @ 2014-10-17 13:15 UTC (permalink / raw)
  To: selinux

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

I started rewriting my policy using name spaces again. I was assuming the the name space issues were fixed.

However I am encountering, what i believe, is an inconsistency.

The block statement is used to declare a name space

in module a i declare the a (root) name space

    (block a
        ...
    )

in module b i declare the b name space in the existing a (root) name space

    (in a
        (block b
            ...
        )
    )

All is well so far... However if i now want to declare the c name space in the existing a.b name space then cilc is unable to resolve the a.b name space

    (in a.b
        (block c
            ...
        )
    )

    "Unable to resolve a.b in in statement..."

The a.b name space exists

The workaround to this inconsistency is to create duplicate declarations:

    (in a
        (block b
            (block c
                ...
            )
        )
    )

Now the b name space is declared two times, but it works around the issue

Why can it not resolve the existing a.b name space?

-- 
Dominick Grift

[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: cilc: name space inconsistency
  2014-10-17 13:15 cilc: name space inconsistency Dominick Grift
@ 2014-10-20 13:34 ` Dominick Grift
  0 siblings, 0 replies; 2+ messages in thread
From: Dominick Grift @ 2014-10-20 13:34 UTC (permalink / raw)
  To: selinux

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

On Fri, Oct 17, 2014 at 03:15:49PM +0200, Dominick Grift wrote:
> I started rewriting my policy using name spaces again. I was assuming the the name space issues were fixed.
> 
> However I am encountering, what i believe, is an inconsistency.

Never mind, its just a warning. I build with -v and sometimes i forget that and get alarmed by any char it returns

[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-10-20 13:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-17 13:15 cilc: name space inconsistency Dominick Grift
2014-10-20 13:34 ` Dominick Grift

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.