diff options
author | 2005-09-09 13:01:35 -0700 | |
---|---|---|
committer | 2005-09-09 13:57:27 -0700 | |
commit | 5e41ff9e0650f327a6c819841fa412da95d57319 (patch) | |
tree | a525df8bda34c2aa52f30326f94cd15109bb58b3 /fs/ext2/xattr_security.c | |
parent | [PATCH] txx9 serial update (diff) | |
download | linux-5e41ff9e0650f327a6c819841fa412da95d57319.tar.gz linux-5e41ff9e0650f327a6c819841fa412da95d57319.tar.bz2 linux-5e41ff9e0650f327a6c819841fa412da95d57319.zip |
[PATCH] security: enable atomic inode security labeling
The following patch set enables atomic security labeling of newly created
inodes by altering the fs code to invoke a new LSM hook to obtain the security
attribute to apply to a newly created inode and to set up the incore inode
security state during the inode creation transaction. This parallels the
existing processing for setting ACLs on newly created inodes. Otherwise, it
is possible for new inodes to be accessed by another thread via the dcache
prior to complete security setup (presently handled by the
post_create/mkdir/... LSM hooks in the VFS) and a newly created inode may be
left unlabeled on the disk in the event of a crash. SELinux presently works
around the issue by ensuring that the incore inode security label is
initialized to a special SID that is inaccessible to unprivileged processes
(in accordance with policy), thereby preventing inappropriate access but
potentially causing false denials on legitimate accesses. A simple test
program demonstrates such false denials on SELinux, and the patch solves the
problem. Similar such false denials have been encountered in real
applications.
This patch defines a new inode_init_security LSM hook to obtain the security
attribute to apply to a newly created inode and to set up the incore inode
security state for it, and adds a corresponding hook function implementation
to SELinux.
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/ext2/xattr_security.c')
0 files changed, 0 insertions, 0 deletions