All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Thomas Liu <tliu@redhat.com>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov, jmorris@namei.org,
	eparis@parisplace.org
Subject: Re: [PATCH 1/4 -v2] Namespacing of security/selinux
Date: Mon, 6 Jul 2009 16:28:06 -0400	[thread overview]
Message-ID: <200907061628.06422.paul.moore@hp.com> (raw)
In-Reply-To: <1246906718.2460.12.camel@Ares>

On Monday 06 July 2009 02:58:38 pm Thomas Liu wrote:
> This patch namespaces the functions in security/selinux, prefixing
> non static functions with selinux_
>
> Patch 1 includes namespacing of the security/selinux folder,
> not including security/selinux/ss.
>
> Added selinux_ as a prefix to non static functions, not including
> functions beginning with avc_.  Swapped security_ with selinux_.

I haven't had a chance to look at all of you patches yet but a few quick 
thoughts in no particular order ...

* Why not prefix functions regardless of if they are static or not?  After 
all, when you are reading the function body of a caller you don't always know 
that the function being called is static.  I personally would find this nice, 
but I might be the only one.

* The "selinux_" prefix seems a tiny bit longer than necessary, how about 
something like "sel_"/"sel_ss_" (we already use SEL in a few places) or 
"selnx_"/"selnx_ss_"?

-- 
paul moore
linux @ hp


--
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.

      parent reply	other threads:[~2009-07-06 20:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 18:58 [PATCH 1/4 -v2] Namespacing of security/selinux Thomas Liu
2009-07-06 19:43 ` Stephen Smalley
2009-07-07 12:06   ` Stephen Smalley
2009-07-07 12:48     ` James Morris
2009-07-07 17:47       ` Eric Paris
2009-07-07 21:49     ` [PATCH 1/2 -v3] " Thomas Liu
2009-08-14 15:20       ` Stephen Smalley
2009-08-14 15:20         ` Eric Paris
2009-08-14 17:28         ` Glenn Faden
2009-08-14 17:47           ` Stephen Smalley
2009-07-06 20:28 ` Paul Moore [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=200907061628.06422.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=tliu@redhat.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.