mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Andrew Morton <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [PATCH 1/4] proc: Properly compute TGID_OFFSET
Date: Sat,  9 Sep 2006 22:01:02 -0600	[thread overview]
Message-ID: <11578608653509-git-send-email-ebiederm@xmission.com> (raw)
In-Reply-To: <m1venwfk43.fsf@ebiederm.dsl.xmission.com>

The value doesn't change but this ensures I will have the proper
value when other files are added to proc_base_stuff.

Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
 fs/proc/base.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/proc/base.c b/fs/proc/base.c
index 04e29f9..c4fcd64 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -1961,7 +1961,7 @@ retry:
 	return task;
 }
 
-#define TGID_OFFSET (FIRST_PROCESS_ENTRY + (1 /* /proc/self */))
+#define TGID_OFFSET (FIRST_PROCESS_ENTRY + (ARRAY_SIZE(proc_base_stuff) - 1))
 
 static int proc_pid_fill_cache(struct file *filp, void *dirent, filldir_t filldir,
 	struct task_struct *task, int tgid)
-- 
1.4.2.rc3.g7e18e-dirty


  reply	other threads:[~2006-09-10  4:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10  3:58 [PATCH 0/4] proc: Misc cleanups Eric W. Biederman
2006-09-10  4:01 ` Eric W. Biederman [this message]
2006-09-10  4:01 ` [PATCH 2/4] proc: Remove trailing blank entry from pid_entry arrays Eric W. Biederman
2006-09-10  4:01 ` [PATCH 3/4] proc: Remove the useless SMP-safe comments from /proc Eric W. Biederman
2006-09-10  4:01 ` [PATCH 4/4] proc: Comment what proc_fill_cache does Eric W. Biederman

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=11578608653509-git-send-email-ebiederm@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.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®