From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [patch0/8] SELinux non trivial fixes.
Date: Wed, 01 Jul 2009 22:38:36 -0700 [thread overview]
Message-ID: <4A4C47DC.90005@gmail.com> (raw)
hmm man!! I used -compose
on the git interface and sent them to myself numerous
times to make sure it works..(I don't know why git didn't send 0/8)
Here's the compose part if it never was sent for some reason:
I decided to sit and manually write out all of the SELinux
area(or at least some of it). So along the way
whenever I saw what might need a bit of cleaning up
I wrote it down, and then once finished
created a patch to submit for you guy's to decide.
So here you go(still need to go into the other directories,
and will later on) but for now hope you like what you see,
and if you see something that might need changing send me a post.
security/selinux/avc.c | 21 ++--
security/selinux/hooks.c | 265
+++++++++++++++++++++---------------------
security/selinux/netif.c | 12 +-
security/selinux/netlabel.c | 10 +-
security/selinux/netnode.c | 20 ++--
security/selinux/netport.c | 12 +-
security/selinux/selinuxfs.c | 61 +++++-----
security/selinux/xfrm.c | 26 ++--
8 files changed, 213 insertions(+), 214 deletions(-)
reply other threads:[~2009-07-02 5:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A4C47DC.90005@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).