From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH] SELinux: Cleanup the secid/secctx conversion functions
Date: Fri, 29 Feb 2008 08:27:28 -0500 [thread overview]
Message-ID: <200802290827.30364.paul.moore@hp.com> (raw)
In-Reply-To: <Xine.LNX.4.64.0802292048010.27014@us.intercode.com.au>
On Friday 29 February 2008 4:49:59 am James Morris wrote:
> On Thu, 28 Feb 2008, Paul Moore wrote:
> > While looking at the SELinux secid/secctx conversion functions I realized
> > they could probably do with a little cleanup to reduce the amount of code
> > and make better use of existing string processing functions in the
> > kernel. Making use of the kernel's existing string processing functions
> > is a good idea as many architectures have specialized/optimized routines
> > which should be an improvement over the generic code in the SELinux
> > security server.
>
> Please always include a signed-off-by line, in case the patch gets
> applied.
Not including my sign-off is intentional as I've found it the only reliable to
keep patches from being merged upstream before I'm happy with them. In this
particular case I've only booted the patch once or twice and was posting it
to see if others felt it worthwhile before I spent any more time on it.
> > -static int context_struct_to_string(struct context *context, char
> > **scontext, u32 *scontext_len) +static int
> > context_struct_to_string(struct context *context,
> > + char **scontext, u32 *scontext_len)
>
> I tend to not prefer the 80-column rule for function declarations, as it
> makes the code harder to grep (not a show-stopper, but generally, don't
> try and fix these).
I find myself sticking pretty religiously to the 80-column rule, but you make
a valid point that if I'm not changing the arguments I probably shouldn't
mess with them. I'll fix that up.
--
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.
next prev parent reply other threads:[~2008-02-29 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 21:41 [RFC PATCH] SELinux: Cleanup the secid/secctx conversion functions Paul Moore
2008-02-29 9:49 ` James Morris
2008-02-29 13:27 ` Paul Moore [this message]
2008-02-29 13:54 ` Stephen Smalley
2008-02-29 14:13 ` Stephen Smalley
2008-02-29 14:23 ` Paul Moore
2008-02-29 16:40 ` James Antill
2008-02-29 17:03 ` Paul Moore
2008-02-29 18:41 ` Todd Miller
2008-02-29 18:58 ` Paul Moore
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=200802290827.30364.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=jmorris@namei.org \
--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.