From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Landley <rob@landley.net>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: execve(NULL, argv, envp) for nommu?
Date: Tue, 5 Sep 2017 14:24:36 +0100 [thread overview]
Message-ID: <20170905142436.262ed118@alans-desktop> (raw)
In-Reply-To: <CAMuHMdUPUaLfbbFF1kZoEUy7or-9sVOt=ykAHT+S6NBvFy5V=g@mail.gmail.com>
> > anymore. But I'm already _running_ this program. If I could fork() I
> > could already get a second copy of the sucker and call main() again
> > myself if necessary, but I can't, so...
You can - ptrace 8)
> > honoring the suid bit if people feel that way. I just wanna unblock
> > vfork() while still running this code.
Would it make more sense to have a way to promote your vfork into a
fork when you hit these cases (I appreciate that fork on NOMMU has a much
higher performance cost as you start having to softmmu copy or swap
pages).
Alan
next prev parent reply other threads:[~2017-09-05 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 7:34 execve(NULL, argv, envp) for nommu? Rob Landley
2017-09-05 9:00 ` Geert Uytterhoeven
2017-09-05 13:24 ` Alan Cox [this message]
2017-09-06 1:12 ` Rob Landley
2017-09-08 21:18 ` Rob Landley
2017-09-11 15:15 ` Oleg Nesterov
2017-09-12 10:48 ` Rob Landley
2017-09-12 11:30 ` Geert Uytterhoeven
2017-09-12 13:45 ` Rob Landley
2017-09-13 19:33 ` Alan Cox
2017-09-12 15:45 ` Oleg Nesterov
2017-09-13 14:20 ` Oleg Nesterov
2017-09-11 18:14 ` Alan Cox
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=20170905142436.262ed118@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rob@landley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.