public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: "Zach, Yoav" <yoav.zach@intel.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Handle non-readable binfmt misc executables
Date: 20 Jun 2004 08:17:16 -0400	[thread overview]
Message-ID: <1087733836.9831.965.camel@cube> (raw)
In-Reply-To: <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>

On Sun, 2004-06-20 at 06:36, Zach, Yoav wrote:
> Albert,
> I'm a little bit confused - I see myself in the CC: list, with no
> recipient in the To: list. I'm not sure this reply will get to all
> the recipients of your message. Will you please forward it to all
> the rest ?

I don't know if I did send it elsewhere. Maybe I had
intended to add linux-kernel.

> Anyways, the problem with the info in /proc can be solved by
> the translator itself in userland. The way it is done in the IA-32
> Execution Layer is by shifting the arguments vector two positions to
> the left, so the user can see the original argument list without the
> additional information the kernel uses for the binfmt_misc mechanism.

So the content of /proc/*/cmdline is correct?

At a minimum, you will have a problem at startup.
The process might be observed before you fix argv.

What about apps that walk off the end of argv to get
at the environment?

It seems cleaner to use some other mechanism.
Assuming your interpreter is ELF, ELF notes are good.
You might use prctl().



       reply	other threads:[~2004-06-20 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>
2004-06-20 12:17 ` Albert Cahalan [this message]
2004-06-23  9:54 [PATCH] Handle non-readable binfmt misc executables Zach, Yoav
  -- strict thread matches above, loose matches on Subject: below --
2004-06-22  7:58 [PATCH] Handle non-readable binfmt_misc executables Zach, Yoav
2004-06-21 11:31 [PATCH] Handle non-readable binfmt misc executables Zach, Yoav
2004-06-21 11:49 ` 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=1087733836.9831.965.camel@cube \
    --to=albert@users.sf.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