Skip to contentSkip to conversation

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

PATCH New David Howells 1 participant 1 message Apr 23, 2009

Subsystems (2)
lore
Share & tools
lore

David Howells

author maintainer
#0 lore raw

PATCH 1/1 CacheFiles: Fix the documentation to use the correct credential pointer names

From: Marc Dionne <[email protected]>

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.

---

 Documentation/filesystems/caching/cachefiles.txt |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
Documentation/filesystems/caching/cachefiles.txt +4 -4
index c78a49b..748a1ae 100644
@@ -407,7 +407,7 @@ A NOTE ON SECURITY
 ==================
 
 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.
 
 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.
 
 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 holds the intrinsic security properties of a process and is
-never overridden.  This is what appears in /proc, and is what is used when a
+objective security (task->real_cred) and the subjective security (task->cred).
+The objective security holds the intrinsic security properties of a process and
+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
 example).