From: "David P. Quigley" <dpquigl-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
To: casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org,
chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org,
sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org,
jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org
Cc: selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org,
linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
nfsv4-6DNke4IJHB0gsBAKwltoeQ@public.gmane.org
Subject: [PATCH]Introduce generalized hooks for getting and setting inode secctx.
Date: Wed, 23 Apr 2008 12:57:14 -0400 [thread overview]
Message-ID: <1208969836-8129-1-git-send-email-dpquigl@tycho.nsa.gov> (raw)
This patch set does two things. First it factors the section of vfs_setxattr
that does the real work into a helper function. This allows LSMs the ability
to set the xattrs they need without hitting the permission check inside
vfs_setxattr each time. Second it introduces three new hooks
inode_{get,set}secctx, and inode_notifysecctx.
The first hook retreives all security information the LSM feels is relavent in
the form of a security context. The second hook given this context can sets
both the in-core and on-disk store for the particular inode. The third hook is
used to notify the in-core inode of a change to it's security state.
This is the fourth revision of this patch set which takes into account
concerns by Casey Schaufler, and Christop Hellwig.
fs/xattr.c | 57 ++++++++++++++++++++++++++++++++++-----------
include/linux/security.h | 50 ++++++++++++++++++++++++++++++++++++++++
include/linux/xattr.h | 1 +
security/dummy.c | 17 +++++++++++++
security/security.c | 18 ++++++++++++++
security/selinux/hooks.c | 28 ++++++++++++++++++++++
6 files changed, 157 insertions(+), 14 deletions(-)
next reply other threads:[~2008-04-23 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 16:57 David P. Quigley [this message]
[not found] ` <1208969836-8129-1-git-send-email-dpquigl-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
2008-04-23 16:57 ` [PATCH 1/2] VFS: Factor out part of vfs_setxattr so it can be called from the SELinux hook for inode_setsecctx David P. Quigley
2008-04-23 16:57 ` [PATCH 2/2] LSM/SELinux: inode_{get,set,notify}secctx hooks to access LSM security context information David P. Quigley
2008-04-27 23:33 ` [PATCH]Introduce generalized hooks for getting and setting inode secctx James Morris
2008-04-28 6:06 ` Christoph Hellwig
2008-04-28 15:04 ` James Morris
2008-04-28 15:10 ` Dave Quigley
2008-04-28 15:02 ` Casey Schaufler
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=1208969836-8129-1-git-send-email-dpquigl@tycho.nsa.gov \
--to=dpquigl-+05t5uksl2qpzymllgbcsa@public.gmane.org \
--cc=casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org \
--cc=chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nfsv4-6DNke4IJHB0gsBAKwltoeQ@public.gmane.org \
--cc=sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org \
--cc=selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.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).