All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, jmorris@namei.org
Subject: Re: [RFC] SELinux: move security_skb_extlbl_sid() out of the security server
Date: Thu, 1 Mar 2007 14:35:08 -0500	[thread overview]
Message-ID: <200703011435.08537.paul.moore@hp.com> (raw)
In-Reply-To: <1172774649.19041.582.camel@moss-spartans.epoch.ncsc.mil>

On Thursday, March 1 2007 1:44:09 pm Stephen Smalley wrote:
> On Thu, 2007-03-01 at 12:34 -0500, Paul Moore wrote:
> > plain text document attachment (selinux-skbextlbl_move)
> > As suggested, move the security_skb_extlbl_sid() function out of the
> > security server and into the SELinux hooks file.
>
> Thanks, but one minor change suggested - rename the function, as
> security_ prefix in selinux means security server (which in turn is
> confusing since LSM also uses that prefix, but we had it first!).  Since
> it is static, you don't even need distinct namespace for it, so even
> skb_extlbl_sid() is fine.

Ah yes, thank you.  I did that in the previous patchset but forgot to do so 
here.  Personally I tend to like the security_/selinux_ prefix (it keeps my 
finger's busy <g>) so I'll just switch from security_ to selinux_.

Patch coming in just a second.

-- 
paul moore
linux security @ 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.

      reply	other threads:[~2007-03-01 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 17:34 [RFC] SELinux: move security_skb_extlbl_sid() out of the security server Paul Moore
2007-03-01 18:44 ` Stephen Smalley
2007-03-01 19:35   ` 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=200703011435.08537.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=jmorris@namei.org \
    --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.