All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmill@redhat.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Michael C Thompson <thompsmc@us.ibm.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	"Christopher J. PeBenito" <cpebenito@tresys.com>,
	SE Linux <selinux@tycho.nsa.gov>
Subject: RE: using cron in selinux policy
Date: Wed, 18 Apr 2007 11:04:10 -0400	[thread overview]
Message-ID: <1176908650.11469.6.camel@localhost.localdomain> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B01588A715EF@exchange.columbia.tresys.com>

On Wed, 2007-04-18 at 10:57 -0400, Joshua Brindle wrote:
> > From: Karl MacMillan [mailto:kmacmill@redhat.com] 
> > 
> > > 
> > > Causes the same problem.  I also got this to happen with 
> > > ethereal_per_role_template.  Compiler says that the type is defined 
> > > twice, even though I only see it once.  However there is a 
> > > gen_requires of the type before the declaration which might 
> > be causing the problem.
> > > 
> > 
> > That's what is causing the problem - can you just remove the requires?
> > Josh - I thought we were going to do promotion of requires at 
> > one point.
> > Did you decide against that?
> > 
> 
> 
> We fixed declare-then-require but for some reason which I can't think of
> right now did not add promotion of requires. We could fix this now or
> wait for the new parser that won't care, how important is this?

Seems like there was a good reason not to but I can't think of it right
now. I think it is a policy bug - so let's punt.

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.

      reply	other threads:[~2007-04-18 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46253DA7.40003@us.ibm.com>
2007-04-18 13:04 ` using cron in selinux policy Daniel J Walsh
2007-04-18 14:22   ` using cron in selinux policy ( a tip) Zwartsenberg, Remmolt
2007-04-18 14:47   ` using cron in selinux policy Karl MacMillan
2007-04-18 14:57     ` Joshua Brindle
2007-04-18 15:04       ` Karl MacMillan [this message]

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=1176908650.11469.6.camel@localhost.localdomain \
    --to=kmacmill@redhat.com \
    --cc=cpebenito@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=thompsmc@us.ibm.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 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.