From: James Morris <jmorris@namei.org>
To: Paul Moore <paul.moore@hp.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH] SELinux: Cleanup the secid/secctx conversion functions
Date: Fri, 29 Feb 2008 20:49:59 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0802292048010.27014@us.intercode.com.au> (raw)
In-Reply-To: <20080228214152.32557.76137.stgit@flek.americas.hpqcorp.net>
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.
> -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).
- James
--
James Morris
<jmorris@namei.org>
--
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 9:50 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 [this message]
2008-02-29 13:27 ` Paul Moore
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=Xine.LNX.4.64.0802292048010.27014@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=paul.moore@hp.com \
--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.