From: ebiederm@xmission.com (Eric W. Biederman)
To: e8607062@student.tuwien.ac.at
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Elliot Lee <sopwith@redhat.com>
Subject: Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)
Date: Sun, 21 Aug 2005 23:15:33 -0600 [thread overview]
Message-ID: <m1zmratuve.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1124326652.8359.3.camel@w2> (Wieland Gmeiner's message of "Thu, 18 Aug 2005 02:57:31 +0200")
Wieland Gmeiner <e8607062@student.tuwien.ac.at> writes:
> (This resembles the behaviour of the ptrace system call.)
ptrace does not solve this problem because?
If you can do this now without a syscall why do you need
a syscall to optimize this code path?
Eric
next prev parent reply other threads:[~2005-08-22 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 0:57 [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update) Wieland Gmeiner
2005-08-18 1:02 ` [PATCH 2.6.13-rc6 2/2] New Syscall: set " Wieland Gmeiner
2005-08-18 1:57 ` Chris Wright
2005-08-18 15:48 ` Stephen Smalley
2005-08-18 1:17 ` [PATCH 2.6.13-rc6 1/2] New Syscall: get " Chris Wright
2005-08-18 2:05 ` Andi Kleen
2005-08-18 16:19 ` Wieland Gmeiner
2005-08-18 16:40 ` James Morris
2005-08-18 17:49 ` Alan Cox
2005-08-19 17:11 ` Elliot Lee
2005-08-23 5:52 ` Ulrich Drepper
2005-08-18 18:17 ` Lee Revell
2005-08-18 23:13 ` Alan Cox
2005-08-18 23:16 ` Lee Revell
2005-08-19 0:29 ` Alan Cox
2005-08-19 0:15 ` Lee Revell
2005-08-22 5:15 ` Eric W. Biederman [this message]
[not found] <1124326652.8359.3.camel@w2.suse.lists.linux.kernel>
[not found] ` <p7364u40zld.fsf@verdi.suse.de.suse.lists.linux.kernel>
[not found] ` <1124381951.6251.14.camel@w2.suse.lists.linux.kernel>
2005-08-18 16:39 ` Andi Kleen
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=m1zmratuve.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=e8607062@student.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=sopwith@redhat.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