From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Karl MacMillan <kmacmill@redhat.com>,
Joshua Brindle <jbrindle@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: There is a bug in checkmodule that is driving me nuts
Date: Mon, 23 Jul 2007 11:00:54 -0400 [thread overview]
Message-ID: <46A4C2A6.80605@mentalrootkit.com> (raw)
In-Reply-To: <46A4BD5F.6070408@redhat.com>
Daniel J Walsh wrote:
> Stephen Smalley wrote:
>> On Fri, 2007-07-20 at 18:28 -0400, Karl MacMillan wrote:
>>
>>> On Fri, 2007-07-20 at 16:22 -0400, Daniel J Walsh wrote:
>>>
>>>> The compiler is mistakenly seeing a
>>>>
>>>> gen_requires {
>>>> type xguest_gnome_home_t;
>>>> }
>>>>
>>>> As a redefinition of the type
>>>>
>>>> /usr/bin/checkmodule -M -m guest.tmp -o
>>>> guest.mod/usr/bin/checkmodule: loading policy configuration from
>>>> guest.tmp
>>>> policy/modules/users/guest.te:4:ERROR 'duplicate declaration of
>>>> type/attribute' at token ';' on line 55020:
>>>> type xguest_gnome_home_t;
>>>> #line 4
>>>> /usr/bin/checkmodule: error(s) encountered while parsing
>>>> configuration
>>>>
>>>> The problem is the gen_requires happens before the declaration.
>>>>
>>>> The type is being declared in a template file.
>>>>
>>> For better or discarding of requires upon hitting a declaration isn't
>>> like to be fixed (when the require is first).
>>>
>>
>> How hard is it to escalate a requires to a decl?
>> Already happens for users and roles, right?
>>
>>
>>> I have an alternative suggestion - remove all of the requires from the
>>> policy and use an sepolgen-based pre-processor to add them back in
>>> until
>>> the policyrep work is done. That will ease the migration and can be
>>> done
>>> far more easily than fixing the current compiler.
>>>
>>> Karl
>>>
>>>
>>> --
>>> This message was distributed to subscribers of the selinux mailing
>>> list.
>>> If you no longer wish to subscribe, send mail to
>>> majordomo@tycho.nsa.gov with
>>> the words "unsubscribe selinux" without quotes as the message.
>>>
> If we resorted Templates before Interfaces, would this problem go away?
>
Potentially - requires after declarations works fine (the requires is
just ignored). The other way around is what is more trouble.
Karl
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to
> majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-07-23 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 20:22 There is a bug in checkmodule that is driving me nuts Daniel J Walsh
2007-07-20 22:28 ` Karl MacMillan
2007-07-21 4:20 ` Shintaro Fujiwara
2007-07-23 14:25 ` Karl MacMillan
2007-07-23 14:30 ` Stephen Smalley
2007-07-23 14:38 ` Daniel J Walsh
2007-07-23 15:00 ` Karl MacMillan [this message]
2007-07-23 16:00 ` Daniel J Walsh
2007-07-23 16:00 ` Daniel J Walsh
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=46A4C2A6.80605@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=kmacmill@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 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.