From: "Claudio Scordino" <cloud.of.andor@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Andy Lutomirski" <luto@myrealbox.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
torvalds@osdl.org, "Andrew Morton" <akpm@osdl.org>,
kernel-janitors@lists.osdl.org
Subject: [PATCH] Extending getrusage
Date: Thu, 20 Apr 2006 17:21:16 +0200 [thread overview]
Message-ID: <d0191dad0604200821l3fa0ed70ga2faabe79d7718ec@mail.gmail.com> (raw)
For the people who missed the beginning of the discussion, the
following patch is an extension of the existing getrusage syscall()
and it applies to the 2.6.16.9 kernel.
It allows a task to read usage information about another task. The argument
who can be equal to RUSAGE_SELF, to RUSAGE_CHILDREN or to a valid pid.
The permissions are checked through security_ptrace() as suggested by Andy.
Any other comment ?
Thanks,
Claudio
Signed-off-by: Claudio Scordino <cloud.of.andor@gmail.com>
--- sys.old.c 2006-04-19 02:10:14.000000000 -0400
+++ sys.c 2006-04-20 10:53:16.000000000 -0400
@@ -1765,11 +1765,30 @@ int getrusage(struct task_struct *p, int
return copy_to_user(ru, &r, sizeof(r)) ? -EFAULT : 0;
}
+/* who can be RUSAGE_SELF, RUSAGE_CHILDREN or a valid pid */
asmlinkage long sys_getrusage(int who, struct rusage __user *ru)
{
- if (who != RUSAGE_SELF && who != RUSAGE_CHILDREN)
- return -EINVAL;
- return getrusage(current, who, ru);
+ struct rusage r;
+ struct task_struct* tsk = current;
+ read_lock(&tasklist_lock);
+ if ((who != RUSAGE_SELF) && (who != RUSAGE_CHILDREN)) {
+ if (who <= 0)
+ goto bad;
+ tsk = find_task_by_pid(who);
+ if (tsk == NULL)
+ goto bad;
+ if ((tsk != current) && security_ptrace(current, tsk))
+ goto bad;
+ /* current can get info about tsk */
+ who = RUSAGE_SELF;
+ }
+ k_getrusage(tsk, who, &r);
+ read_unlock(&tasklist_lock);
+ return copy_to_user(ru, &r, sizeof(r)) ? -EFAULT : 0;
+
+bad:
+ read_unlock(&tasklist_lock);
+ return tsk ? -EPERM : -EINVAL;
}
asmlinkage long sys_umask(int mask)
next reply other threads:[~2006-04-20 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 15:21 Claudio Scordino [this message]
2006-04-20 23:21 ` [PATCH] Extending getrusage Andrew Morton
2006-04-21 7:41 ` bert hubert
2006-04-21 10:05 ` Claudio Scordino
2006-04-21 14:32 ` Ulrich Drepper
2006-04-22 10:25 ` Claudio Scordino
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=d0191dad0604200821l3fa0ed70ga2faabe79d7718ec@mail.gmail.com \
--to=cloud.of.andor@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
--cc=torvalds@osdl.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