All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, Karl MacMillan <kmacmillan@tresys.com>
Subject: Re: [10 / 9] [ SEMANAGE ] FIx placement of function table
Date: Fri, 30 Sep 2005 16:56:04 -0400	[thread overview]
Message-ID: <433DA664.6040600@cornell.edu> (raw)
In-Reply-To: <1128112109.12459.216.camel@moss-spartans.epoch.ncsc.mil>


>Hmmm...I just got done merging the others (available in the sourceforge
>CVS), although naturally all of this is still open to debate and can be
>reverted at any time.
>
>I think at this point I'll wait for clarification from Karl et al on
>whether this patch (and the prior ones as well) are consistent with
>their plans for libsemanage.
>  
>
Okay...

It's just a question of where things are supposed to be placed. I think 
Karl agreed earlier that headers should follow the code, and that's what 
I was thinking about, but my first patch moved things to the wrong places.

----
The policy function table being discussed is an interface (to be used 
for the purposes of polymorphism). Because this is an interface, there 
is no associated code - implementations use the specific type, and 
include a header to fill the table . At the same time, 
semanage_private.h was containing random things, so this is probably 
better off on its own, which this patch sets up (or bundled with the 
rest of interfaces.h, but handle.h is probably the wrong place for it).

The other thing I moved was handle code (that's fine IMHO), debug code 
(fine), and a conn object. I can't figure out exactly what the conn 
object is planned for, so that's why I asked... I suspect it's the 
connection state object for direct API (so it goes in direct_api.h)

--
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:[~2005-09-30 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 20:30 [10 / 9] [ SEMANAGE ] FIx placement of function table Ivan Gyurdiev
2005-09-30 20:28 ` Stephen Smalley
2005-09-30 20:56   ` Ivan Gyurdiev [this message]
2005-10-01  0:19     ` [ SEMANAGE ] [ SEPOL ] Backend iterate function Ivan Gyurdiev
2005-10-01  1:49       ` [ SEMANAGE ] Break up interfaces.h, implement parsing helpers Ivan Gyurdiev
2005-10-04 14:54         ` Stephen Smalley
2005-10-04 14:53       ` [ SEMANAGE ] [ SEPOL ] Backend iterate function Stephen Smalley
2005-10-03 13:47   ` [10 / 9] [ SEMANAGE ] FIx placement of function table Karl MacMillan
2005-10-04 14:53 ` Stephen Smalley
2005-10-04 15:52   ` Synchronization/Caching Ivan Gyurdiev

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=433DA664.6040600@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=kmacmillan@tresys.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.