dect
/
linux-2.6
Archived
13
0
Fork 0
Code Releases Activity

CacheFiles: Fix the documentation to use the correct credential pointer names 

Adjust the CacheFiles documentation to use the correct names of the credential
pointers in task_struct.

The documentation was using names from the old versions of the credentials
patches.

Signed-off-by: Marc Dionne <marc.c.dionne@gmail.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Marc Dionne 2009-04-23 11:21:55 +01:00 committed by Linus Torvalds
parent e5b89542ea
commit 91ac033d83
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/filesystems/caching/cachefiles.txt
View File

@ -407,7 +407,7 @@ A NOTE ON SECURITY
================== ==================
CacheFiles makes use of the split security in the task_struct. It allocates CacheFiles makes use of the split security in the task_struct. It allocates
its own task_security structure, and redirects current->act_as to point to it its own task_security structure, and redirects current->cred to point to it
when it acts on behalf of another process, in that process's context. when it acts on behalf of another process, in that process's context.
The reason it does this is that it calls vfs_mkdir() and suchlike rather than The reason it does this is that it calls vfs_mkdir() and suchlike rather than
@ -429,9 +429,9 @@ This means it may lose signals or ptrace events for example, and affects what
the process looks like in /proc. the process looks like in /proc.
So CacheFiles makes use of a logical split in the security between the So CacheFiles makes use of a logical split in the security between the
objective security (task->sec) and the subjective security (task->act_as). The objective security (task->real_cred) and the subjective security (task->cred).
objective security holds the intrinsic security properties of a process and is The objective security holds the intrinsic security properties of a process and
never overridden. This is what appears in /proc, and is what is used when a is never overridden. This is what appears in /proc, and is what is used when a
process is the target of an operation by some other process (SIGKILL for process is the target of an operation by some other process (SIGKILL for
example). example).