From: Ray Lee <ray-lk@madrabbit.org>
To: Rob Landley <rob@landley.net>
Cc: Vadim Lobanov <vlobanov@speakeasy.net>,
ray-gmail@madrabbit.org, linux-kernel@vger.kernel.org,
David McCullough <david_mccullough@au.securecomputing.com>
Subject: Re: Feature request: exec self for NOMMU.
Date: Wed, 27 Dec 2006 10:49:28 -0800 [thread overview]
Message-ID: <4592C038.8010407@madrabbit.org> (raw)
In-Reply-To: <200612270329.16320.rob@landley.net>
Rob Landley wrote:
> On Wednesday 27 December 2006 1:08 am, Vadim Lobanov wrote:
>> On Wed, 2006-12-27 at 00:51 -0500, Rob Landley wrote:
>>> On Wednesday 27 December 2006 12:13 am, Ray Lee wrote:
>>>> How about openning an fd to yourself at the beginning of execution, then
>>>> calling fexecve later?
>>> I haven't got a man page for fexecve. Does libc have it?
>> It's implemented inside glibc, and uses /proc to execve() the file that
>> the fd points to.
Oh, hmm. Then I think it won't work, will it? I'd assumed fexecve was
implemented in kernel.
> Cute, and I can do that. Assuming /proc is mounted in the chroot
> environment...
Maybe I'm just confused -- wouldn't be the first time -- but if it's
implemented inside userspace, then once you chroot() you won't be able
to execute the path you find via /proc, will you?
next prev parent reply other threads:[~2006-12-27 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 23:23 Feature request: exec self for NOMMU Rob Landley
2006-12-26 23:55 ` David Lang
2006-12-27 0:39 ` Rob Landley
2006-12-27 4:24 ` Denis Vlasenko
2006-12-27 5:44 ` Rob Landley
2006-12-27 5:13 ` Ray Lee
2006-12-27 5:51 ` Rob Landley
2006-12-27 6:08 ` Vadim Lobanov
2006-12-27 8:29 ` Rob Landley
2006-12-27 18:49 ` Ray Lee [this message]
2006-12-27 21:13 ` Rob Landley
2006-12-27 18:35 ` Denis Vlasenko
2006-12-27 21:03 ` Rob Landley
2006-12-28 2:48 ` Denis Vlasenko
2006-12-28 5:32 ` Rob Landley
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=4592C038.8010407@madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=david_mccullough@au.securecomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-gmail@madrabbit.org \
--cc=rob@landley.net \
--cc=vlobanov@speakeasy.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;
as well as URLs for NNTP newsgroup(s).