From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
selinux@tycho.nsa.gov
Subject: [PATCH 0/8] security: Use a more current logging style
Date: Mon, 24 Feb 2014 13:59:53 -0800 [thread overview]
Message-ID: <cover.1393279025.git.joe@perches.com> (raw)
Mostly trivial cleanups of security modules
Joe Perches (8):
security: Use a more current logging style
security: apparmor: Use a more current logging style
security: integrity: Use a more current logging style
security: keys: Use a more current logging style
security: selinux: Use a more current logging style
security: smack: Use a more current logging style
security: tomoyo: Use a more current logging style
security: yama: Use a more current logging style
security/apparmor/apparmorfs.c | 2 +
security/apparmor/crypto.c | 2 +
security/apparmor/include/apparmor.h | 2 +-
security/apparmor/lib.c | 4 +-
security/apparmor/lsm.c | 2 +
security/apparmor/match.c | 5 +-
security/apparmor/policy.c | 2 +
security/apparmor/procattr.c | 2 +
security/capability.c | 16 ++--
security/commoncap.c | 15 ++--
security/integrity/evm/evm_crypto.c | 4 +-
security/integrity/evm/evm_main.c | 6 +-
security/integrity/evm/evm_secfs.c | 6 +-
security/integrity/ima/ima_crypto.c | 4 +-
security/integrity/ima/ima_init.c | 5 +-
security/integrity/ima/ima_queue.c | 8 +-
security/integrity/ima/ima_template.c | 5 +-
security/keys/encrypted-keys/encrypted.c | 70 ++++++++---------
security/keys/encrypted-keys/encrypted.h | 2 +-
security/keys/key.c | 2 +
security/keys/trusted.c | 42 +++++-----
security/keys/trusted.h | 20 ++---
security/security.c | 4 +-
security/selinux/avc.c | 7 +-
security/selinux/hooks.c | 130 +++++++++++++------------------
security/selinux/netif.c | 14 ++--
security/selinux/netlink.c | 5 +-
security/selinux/netnode.c | 6 +-
security/selinux/netport.c | 7 +-
security/selinux/selinuxfs.c | 19 ++---
security/selinux/ss/avtab.c | 39 +++++-----
security/selinux/ss/conditional.c | 18 +++--
security/selinux/ss/ebitmap.c | 21 +++--
security/selinux/ss/policydb.c | 109 ++++++++++++--------------
security/selinux/ss/services.c | 101 ++++++++++--------------
security/selinux/ss/sidtab.c | 8 +-
security/smack/smack_lsm.c | 7 +-
security/smack/smackfs.c | 25 +++---
security/tomoyo/common.c | 23 +++---
security/tomoyo/domain.c | 8 +-
security/tomoyo/load_policy.c | 9 ++-
security/tomoyo/memory.c | 7 +-
security/tomoyo/tomoyo.c | 4 +-
security/tomoyo/util.c | 7 +-
security/yama/yama_lsm.c | 18 ++---
45 files changed, 404 insertions(+), 418 deletions(-)
--
1.8.1.2.459.gbcd45b4.dirty
next reply other threads:[~2014-02-24 22:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 21:59 Joe Perches [this message]
2014-02-24 21:59 ` [PATCH 1/8] security: Use a more current logging style Joe Perches
2014-02-25 19:10 ` Serge Hallyn
2014-02-25 19:34 ` Joe Perches
2014-02-25 19:41 ` [PATCH V2 " Joe Perches
2014-02-24 21:59 ` [PATCH 2/8] security: apparmor: " Joe Perches
2014-02-26 7:31 ` John Johansen
2014-02-26 14:43 ` Joe Perches
2014-02-24 21:59 ` [PATCH 3/8] security: integrity: " Joe Perches
2014-02-25 2:59 ` Mimi Zohar
2014-02-24 21:59 ` [PATCH 4/8] security: keys: " Joe Perches
2014-02-24 21:59 ` [PATCH 5/8] security: selinux: " Joe Perches
2014-02-25 20:05 ` Paul Moore
2014-02-25 20:20 ` Joe Perches
2014-02-24 21:59 ` [PATCH 6/8] security: smack: " Joe Perches
2014-02-24 22:16 ` Casey Schaufler
2014-02-24 22:23 ` Joe Perches
2014-02-24 22:33 ` Casey Schaufler
2014-02-24 22:35 ` Casey Schaufler
2014-02-24 23:01 ` Casey Schaufler
2014-02-25 7:47 ` James Morris
[not found] ` <17D2BA68-5581-4326-B6DD-5EC959235B71@aol.com>
2014-02-26 0:56 ` Joe Perches
2014-02-24 22:00 ` [PATCH 7/8] security: tomoyo: " Joe Perches
2014-02-25 12:58 ` Tetsuo Handa
2014-02-24 22:00 ` [PATCH 8/8] security: yama: " Joe Perches
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=cover.1393279025.git.joe@perches.com \
--to=joe@perches.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox