From: Albert Cahalan <albert@users.sf.net>
To: "Zach, Yoav" <yoav.zach@intel.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Handle non-readable binfmt misc executables
Date: 21 Jun 2004 07:49:46 -0400 [thread overview]
Message-ID: <1087818586.8185.1006.camel@cube> (raw)
In-Reply-To: <2C83850C013A2540861D03054B478C060416C175@hasmsx403.ger.corp.intel.com>
On Mon, 2004-06-21 at 07:31, Zach, Yoav wrote:
> >From: Albert Cahalan [mailto:albert@users.sourceforge.net]
> >So the content of /proc/*/cmdline is correct?
>
> After the translator fixes it - yes.
>
> >At a minimum, you will have a problem at startup.
> >The process might be observed before you fix argv.
>
> Right. It might happen once in a (long) while that
> 'ps -f' doesn't show the correct command line.
So this is a hole in the emulation.
> >It seems cleaner to use some other mechanism.
> >Assuming your interpreter is ELF, ELF notes are good.
>
> Using ELF notes means changing the binaries, which is not
> suitable for cases where the use of translator for running
> the binaries is not 'known' to the binaries. For example,
> an administrator might start using a translator to enhance
> performance of existing binaries. In such a case, re-building
> the binaries will probably be out of the question.
No. Well, the translator would change. The old i386
binaries would not.
ELF notes are supplied by the kernel. They provide
data like USER_HZ, the UID, a flag to indicate that
ld.so must take setuid-type precautions, and so on.
ELF notes are on the stack, beyond the environment.
> >You might use prctl().
>
> Do you mean enhancing sys_prctl to allow for fixing
> the argv ?
No. I mean enhancing sys_prctl to allow asking for
the file descriptor number. That way, argv doesn't
need to get mangled in the first place.
I'm sure there are many other good ways to pass the
file descriptor number to the interpreter.
next prev parent reply other threads:[~2004-06-21 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 11:31 [PATCH] Handle non-readable binfmt misc executables Zach, Yoav
2004-06-21 11:49 ` Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 9:54 Zach, Yoav
2004-06-22 7:58 [PATCH] Handle non-readable binfmt_misc executables Zach, Yoav
[not found] <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>
2004-06-20 12:17 ` [PATCH] Handle non-readable binfmt misc executables Albert Cahalan
2004-06-20 10:41 [PATCH] Handle non-readable binfmt_misc executables Zach, Yoav
2004-06-20 10:50 ` Arjan van de Ven
[not found] <200406181612.i5IGCIYY001854@hera.kernel.org>
2004-06-19 14:38 ` Arjan van de Ven
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=1087818586.8185.1006.camel@cube \
--to=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yoav.zach@intel.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