02 Feb, 2011
1 commit
-
SELinux would like to implement a new labeling behavior of newly created
inodes. We currently label new inodes based on the parent and the creating
process. This new behavior would also take into account the name of the
new object when deciding the new label. This is not the (supposed) full path,
just the last component of the path.This is very useful because creating /etc/shadow is different than creating
/etc/passwd but the kernel hooks are unable to differentiate these
operations. We currently require that userspace realize it is doing some
difficult operation like that and than userspace jumps through SELinux hoops
to get things set up correctly. This patch does not implement new
behavior, that is obviously contained in a seperate SELinux patch, but it
does pass the needed name down to the correct LSM hook. If no such name
exists it is fine to pass NULL.Signed-off-by: Eric Paris
22 May, 2010
1 commit
-
Signed-off-by: Stephen Hemminger
Signed-off-by: Al Viro
18 Dec, 2009
1 commit
-
Pass transaction handle down to security and ACL initialization
functions, so we can avoid starting nested transactionsSigned-off-by: Yan Zheng
Signed-off-by: Chris Mason
04 Feb, 2009
1 commit
-
Add call to LSM security initialization and save
resulting security xattr for new inodes.Add xattr support to symlink inode ops.
Set inode->i_op for existing special files.
Signed-off-by: jim owens
25 Sep, 2008
3 commits
-
btrfs actually stores the whole xattr name, including the prefix ondisk,
so using the generic resolver that strips off the prefix is not very
helpful. Instead do the real ondisk xattrs manually and only use the
generic resolver for synthetic xattrs like ACLs.(Sorry Josef for guiding you towards the wrong direction here intially)
Signed-off-by: Christoph Hellwig
Signed-off-by: Chris Mason -
The ->list handler is really not useful at all, because we always call
btrfs_xattr_generic_list anyway. After this is done
find_btrfs_xattr_handler becomes unused, and it becomes obvious that the
temporary name buffer allocation isn't needed but we can directly copy
into the supplied buffer.Tested with various getfattr -d calls on varying xattr lists.
Signed-off-by: Christoph Hellwig
Signed-off-by: Chris Mason -
Signed-off-by: Chris Mason
