From: Claudio Scordino <cloud.of.andor@gmail.com>
To: "Magnus Naeslund(f)" <mag@fbab.net>
Cc: "Hua Zhong (hzhong)" <hzhong@cisco.com>,
linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: [PATCH] getrusage sucks
Date: Fri, 11 Nov 2005 02:11:04 +0100 [thread overview]
Message-ID: <200511110211.05642.cloud.of.andor@gmail.com> (raw)
In-Reply-To: <4373E69B.6040206@fbab.net>
> You need to wrap this with a read_lock(&tasklist_lock) to be safe, I think.
Right. Probably this was the meaning also of Hua's mail. Sorry, but I didn't
get it immediately.
So, what if I do as follows ? Do you see any problem with this solution ?
Many thanks,
Claudio
diff --git a/kernel/sys.c b/kernel/sys.c
--- a/kernel/sys.c
+++ b/kernel/sys.c
@@ -1746,9 +1746,22 @@ int getrusage(struct task_struct *p, int
asmlinkage long sys_getrusage(int who, struct rusage __user *ru)
{
- if (who != RUSAGE_SELF && who != RUSAGE_CHILDREN)
- return -EINVAL;
- return getrusage(current, who, ru);
+ int res;
+ if (who != RUSAGE_SELF && who != RUSAGE_CHILDREN) {
+ struct task_struct* tsk;
+ read_lock(&tasklist_lock);
+ tsk = find_task_by_pid(who);
+ if (tsk == NULL) {
+ read_unlock(&tasklist_lock);
+ return -EINVAL;
+ }
+ res = getrusage(tsk, RUSAGE_SELF, ru);
+ read_unlock(&tasklist_lock);
+ return res;
+ } else {
+ res = getrusage(current, who, ru);
+ return res;
+ }
}
asmlinkage long sys_umask(int mask)
next prev parent reply other threads:[~2005-11-11 1:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 23:47 [PATCH] getrusage sucks Hua Zhong (hzhong)
2005-11-11 0:23 ` Claudio Scordino
2005-11-11 0:32 ` Magnus Naeslund(f)
2005-11-11 1:11 ` Claudio Scordino [this message]
2005-11-11 13:30 ` Alan Cox
2005-11-11 22:38 ` Claudio Scordino
2005-11-11 23:23 ` Alan Cox
2005-11-11 23:02 ` Chris Wright
2005-11-11 23:44 ` David Wagner
2005-11-12 0:53 ` Chris Wright
2005-11-12 6:37 ` David Wagner
2005-11-11 23:58 ` Alan Cox
2005-11-11 23:43 ` Claudio Scordino
2005-11-11 23:49 ` dean gaudet
2005-11-12 1:10 ` Chris Wright
2005-11-12 15:10 ` making makefile for 2.6 kernel anil dahiya
2005-11-12 15:16 ` anil dahiya
2005-11-12 22:19 ` Sam Ravnborg
2005-11-13 1:34 ` [PATCH] getrusage sucks Claudio Scordino
2005-11-15 16:56 ` Claudio Scordino
2005-11-15 17:00 ` New getrusage Claudio Scordino
2005-11-11 23:08 ` [PATCH] getrusage sucks Claudio Scordino
2005-11-11 23:41 ` David Wagner
2005-11-15 1:08 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2005-11-15 18:25 linux
2005-11-11 23:49 Hua Zhong (hzhong)
2005-11-10 22:34 Claudio Scordino
2005-11-11 5:06 ` David Wagner
2005-11-11 19:09 ` Lee Revell
2005-11-11 19:13 ` David Wagner
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=200511110211.05642.cloud.of.andor@gmail.com \
--to=cloud.of.andor@gmail.com \
--cc=hzhong@cisco.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mag@fbab.net \
/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