mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ryan C. Gordon" <icculus@icculus.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/2] binfmt_elf: FatELF support in the binary loader.
Date: Fri, 23 Oct 2009 20:25:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.OSX.1.10.0910232021000.2186@caridad.icculuslan> (raw)
In-Reply-To: <4AE22B34.7090103@goop.org>


> It would be nice to have something that would conceptually work for
> other architectures with other executable file formats.  Granted ELF is
> most common, but its far from the only one.

It would be nice, but I'm not certain it's practical. I mean, if we embed 
a Windows .exe in there, Windows is never going to be able to load it, I 
presume.

That being said, I suppose there's no reason you _couldn't_ do that with 
the existing FatELF format. Just add an OSABI for, say, Windows PE files 
and embed one like anything else. Non-Windows platforms will ignore it 
because it's the wrong OSABI. If something tried to process it as an ELF 
file, it'll correctly believe it to be a corrupt file.

(Replace Windows with your favorite non-ELF platform if you like.)

This isn't really a goal of the project, but since you brought it up, it 
IS actually feasible with the existing code and framework.

> Well, its really a bit diseased, with lots of gristly bits and a few
> unexpected tubes sticking out the side.

Eww.

--ryan.



  reply	other threads:[~2009-10-24  0:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:39 Ryan C. Gordon
2009-10-20  0:12 ` Jeremy Fitzhardinge
2009-10-20  4:43   ` Ryan C. Gordon
2009-10-23 22:16     ` Jeremy Fitzhardinge
2009-10-24  0:25       ` Ryan C. Gordon [this message]
2009-10-21  8:08 ` Ryan C. Gordon
2009-10-22  7:31 ` Nicholas Miell
2009-10-22  9:22   ` Ryan C. Gordon

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=alpine.OSX.1.10.0910232021000.2186@caridad.icculuslan \
    --to=icculus@icculus.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®