From: Geunsik Lim <leemgs1@gmail.com>
To: Jiri Kosina <trivial@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] trivial: helpful task_struct remarks
Date: Wed, 17 Aug 2011 22:36:43 +0900 [thread overview]
Message-ID: <1313588203-7489-1-git-send-email-leemgs1@gmail.com> (raw)
From: Geunsik Lim <geunsik.lim@samsung.com>
This is trivial patch for helpful description of task_struct elements.
'???' remark is not good as a description of data structure.
And, append description information about the meanings of pid and tgid.
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
---
include/linux/sched.h | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 4ac2c05..1a078f8 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1293,8 +1293,7 @@ struct task_struct {
int exit_code, exit_signal;
int pdeath_signal; /* The signal sent when the parent dies */
unsigned int jobctl; /* JOBCTL_*, siglock protected */
- /* ??? */
- unsigned int personality;
+ unsigned int personality; /* Personality types of process */
unsigned did_exec:1;
unsigned in_execve:1; /* Tell the LSMs that the process is doing an
* execve */
@@ -1305,8 +1304,8 @@ struct task_struct {
unsigned sched_reset_on_fork:1;
unsigned sched_contributes_to_load:1;
- pid_t pid;
- pid_t tgid;
+ pid_t pid; /* Process ID, return value of gettid system call */
+ pid_t tgid; /* Thread group ID, return value of getpid system call */
#ifdef CONFIG_CC_STACKPROTECTOR
/* Canary value for the -fstack-protector gcc feature */
--
1.7.1
reply other threads:[~2011-08-17 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1313588203-7489-1-git-send-email-leemgs1@gmail.com \
--to=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trivial@kernel.org \
/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®