linux-kernel - [PATCH] CRED: Use correct task_struct members in cred.h comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080925140335.12957.38478.stgit@warthog.procyon.org.uk>
Date:	Thu, 25 Sep 2008 15:03:37 +0100
From:	David Howells <dhowells@...hat.com>
To:	jmorris@...ei.org
Cc:	dhowells@...hat.com, marc.c.dionne@...il.com,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] CRED: Use correct task_struct members in cred.h comments

From: Marc Dionne <marc.c.dionne@...il.com>

Adjust comments in linux/cred.h - use the correct names for the struct cred
pointers in the task_struct structure.

Signed-off-by: Marc Dionne <marc.c.dionne@...il.com>
Signed-off-by: David Howells <dhowells@...hat.com>
---

 include/linux/cred.h |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)


diff --git a/include/linux/cred.h b/include/linux/cred.h
index 1f8d8d0..26c1ab1 100644
--- a/include/linux/cred.h
+++ b/include/linux/cred.h
@@ -101,14 +101,14 @@ struct thread_group_cred {
  * Note that some members of this structure belong to both categories - the
  * LSM security pointer for instance.
  *
- * A task has two security pointers.  task->sec points to the objective context
- * that defines that task's actual details.  The objective part of this context
- * is used whenever that task is acted upon.
+ * A task has two security pointers.  task->real_cred points to the objective
+ * context that defines that task's actual details.  The objective part of this
+ * context is used whenever that task is acted upon.
  *
- * task->act_as points to the subjective context that defines the details of
- * how that task is going to act upon another object.  This may be overridden
+ * task->cred points to the subjective context that defines the details of how
+ * that task is going to act upon another object.  This may be overridden
  * temporarily to point to another security context, but normally points to the
- * same context as task->sec.
+ * same context as task->real_cred.
  */
 struct cred {
 	atomic_t	usage;

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/