mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, marc.c.dionne@gmail.com,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] CRED: Use correct task_struct members in cred.h comments
Date: Thu, 25 Sep 2008 15:03:37 +0100	[thread overview]
Message-ID: <20080925140335.12957.38478.stgit@warthog.procyon.org.uk> (raw)

From: Marc Dionne <marc.c.dionne@gmail.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@gmail.com>
Signed-off-by: David Howells <dhowells@redhat.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;


             reply	other threads:[~2008-09-25 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 14:03 David Howells [this message]
2008-09-25 21:56 ` James Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080925140335.12957.38478.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=marc.c.dionne@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®