Subject: RE: [PATCH] Handle non-readable binfmt misc executables
From: Albert Cahalan <albert@users.sf.net>
To: "Zach, Yoav" <yoav.zach@intel.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
In-Reply-To: <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>
References: <2C83850C013A2540861D03054B478C060416BC0E@hasmsx403.ger.corp.intel.com>
Content-Type: text/plain
Organization: 
Message-Id: <1087733836.9831.965.camel@cube>
Mime-Version: 1.0
Date: 20 Jun 2004 08:17:16 -0400
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1299
Lines: 34

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().


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/