From: Arjan van de Ven <arjan@infradead.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH]: proc: export a processes resource limits via proc/<pid>
Date: Mon, 13 Aug 2007 08:47:10 -0700 [thread overview]
Message-ID: <1187020030.2688.1.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070813140044.GB1960@hmsreliant.think-freely.org>
On Mon, 2007-08-13 at 10:00 -0400, Neil Horman wrote:
> Hey there-
> Currently, there exists no method for a process to query the resource
> limits of another process. They can be inferred via some mechanisms but they
> cannot be explicitly determined. Given that this information can be usefull to
> know during the debugging of an application, I've written this patch which
> exports all of a processes limits via /proc/<pid>/limits. Tested successfully
> by myself on x86 on top of 2.6.23-rc2-mm1.
since this information, by it's nature, is security sensitive, I would
really really strongly suggest that you make this restricted to those
processes that can ptrace the victim only... (which is basically "same
user or root")
Making this world readable is very much a bad thing to do
next prev parent reply other threads:[~2007-08-13 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 14:00 Neil Horman
2007-08-13 15:47 ` Arjan van de Ven [this message]
2007-08-13 16:47 ` Valdis.Kletnieks
2007-08-13 17:26 ` Neil Horman
2007-08-13 19:25 ` Ingo Oeser
2007-08-13 20:11 ` Neil Horman
2007-08-13 21:04 ` Alexey Dobriyan
2007-08-13 23:58 ` Neil Horman
2007-08-16 12:35 ` Neil Horman
2007-08-17 8:09 ` Valdis.Kletnieks
2007-08-17 10:59 ` Neil Horman
2007-08-17 19:45 ` Andrew Morton
2007-08-17 20:20 ` Valdis.Kletnieks
2007-08-17 21:00 ` Neil Horman
2007-08-21 18:56 ` Andy Isaacson
2007-08-23 2:40 ` Matt Mackall
2007-08-23 10:53 ` Neil Horman
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=1187020030.2688.1.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=torvalds@linux-foundation.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®