From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Bodo Eggert <7eggert@gmx.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Subject: Re: [PATCH] add umask parameter to procfs
Date: Sat, 19 Feb 2005 01:29:03 +0100 [thread overview]
Message-ID: <20050219002903.GA5380@lsrfire.ath.cx> (raw)
In-Reply-To: <20050218035601.GA21343@mail.13thfloor.at>
On Fri, Feb 18, 2005 at 04:56:01AM +0100, Herbert Poetzl wrote:
> hmm, so what about debugger and similar not able to find the
> parent process or something like that?
You can walk the parentage chain up until you reach your login shell.
So you can look up info about the parent of every one of your processes
except for your login shell and any zombies.
> I'd say this needs some more investigation what tools and
> applications will break once it is enabled ...
Sure, that can't be bad. I didn't really do anything so far that
warrants being called testing (compiles, runs, doesn't crash on boot --
send patch! ;).
But I also didn't invent this feature: it has been in OpenWall and
grsecurity for a long time now, so a form of restricted /proc has
received at least *some* testing.
Rene
next prev parent reply other threads:[~2005-02-19 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.h7bdq0l.im6ej1@ifi.uio.no>
[not found] ` <fa.fep4kfp.gmci2d@ifi.uio.no>
2005-02-18 3:22 ` [PATCH] add umask parameter to procfs Bodo Eggert
2005-02-18 3:56 ` Herbert Poetzl
2005-02-19 0:29 ` Rene Scharfe [this message]
2005-02-17 21:28 Rene Scharfe
2005-02-17 23:41 ` Andrew Morton
2005-02-18 1:50 ` Herbert Poetzl
2005-02-18 23:44 ` Debian User
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=20050219002903.GA5380@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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