All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Antill <jantill@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [RFC][PATCH] libselinux: Namespacing
Date: Thu, 10 May 2007 18:12:34 -0400	[thread overview]
Message-ID: <1178835154.12294.151.camel@code.and.org> (raw)
In-Reply-To: <1178827922.3504.141.camel@moss-spartans.epoch.ncsc.mil>

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

On Thu, 2007-05-10 at 16:12 -0400, Stephen Smalley wrote:
> libselinux presently lacks proper namespacing of its functions.  This
> patch is just for comment on an approach to gradually fixing that
> problem, starting with just a trivial example for a single function.
> The idea is to switch over the real function to being properly
> namespaced, provide an alias under the old name in the symbol table for
> binary compatibility, and make the old name a macro in the public
> headers that expands to the new name so that source rebuilds against the
> new library will start using the new name.  Then at some point in the
> future, we drop the old name macro from the source API, forcing an
> update to external sources to build against newer headers, while leaving
> the alias present in the symbol table as long as we need compatibility
> with existing binaries.  Thoughts?

 The one thing I'd suggest is having some kind of compiler switch we can
use before we turn it off. For instance something like...


#ifndef SELINUX_COMPAT_API
#define SELINUX_COMPAT_API 1
#endif

#if SELINUX_COMPAT_API

/* ... */
#define freecon(x) selinux_freecon(x)
#endif

...then we can move certain packages over immediately, and do "#define
SELINUX_COMPAT_API 0" in them ... and also change the default at some
point, but allow people to still access the compat. macros for a short
time.

 Also we really want to have some perl/whatever that goes through the
public API looking for symbols ... so we only have to do it once.

-- 
James Antill <jantill@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-05-10 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 20:12 [RFC][PATCH] libselinux: Namespacing Stephen Smalley
2007-05-10 20:31 ` Karl MacMillan
2007-05-11 12:37   ` Stephen Smalley
2007-05-11 18:37     ` Karl MacMillan
2007-05-29 19:17       ` Eamon Walsh
2007-05-30 14:45         ` Stephen Smalley
2007-05-31 16:27           ` Karl MacMillan
2007-05-10 22:12 ` James Antill [this message]
2007-05-11 12:42   ` Stephen Smalley
2007-05-11 12:47     ` Stephen Smalley
2007-05-11 14:39       ` James Antill

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=1178835154.12294.151.camel@code.and.org \
    --to=jantill@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.