public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinz-Ado Arnolds <Ado.Arnolds@dhm-systems.de>
To: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
	alan@lxorguk.ukuu.org.uk
Subject: Re: fs/exec.c and binfmt-xxx in 2.4.14
Date: Thu, 22 Nov 2001 12:47:07 +0100	[thread overview]
Message-ID: <3BFCE5BB.AD59B011@web-systems.net> (raw)
In-Reply-To: <3BFBDD32.434AB47B@web-systems.net> <20011121211433.B1424@devcon.net>

Andreas Ferber wrote:
> 
> On Wed, Nov 21, 2001 at 05:58:26PM +0100, Heinz-Ado Arnolds wrote:
> >
> > When i now try to start an older binary in a.out format, which has a
> > magic number of 0x010b0064, it is translated with the 'new' code to a
> > request for "binfmt-0064" instead of "binfmt-267" as expected and
> > properly handled by modprobe.
> 
> Then add
> 
> alias binfmt-0064 binfmt_aout
> 
> to /etc/modules.conf. Simple, isn't it?

That's a nice idea but I wouldn't rely on the fact that the third
and the fourth byte of a file are sufficient to identify the type.
If you look at the magic numbers in /etc/magic, you'll find:

  0x00640107      Linux/i386 impure executable (OMAGIC)
  0x00640108      Linux/i386 pure executable (NMAGIC)
  0x0064010b      Linux/i386 demand-paged executable (ZMAGIC)
  0x006400cc      Linux/i386 demand-paged executable (QMAGIC)
  =0514           80386 COFF executable

It's standard to count on the first (and eventually following) bytes.

And if you look further on in /etc/magic, you'll see that there are
other file types having 0x0064 as 3rd and 4th byte.

I think it would not be a great deal to revert the changes in fs/exec.c

Thanks for your attention

Ado

-- 
------------------------------------------------------------------------
  Heinz-Ado Arnolds                        Ado.Arnolds@web-systems.net
  Websystems GmbH                              +49 2234 1840-0 (voice)
  Max-Planck-Strasse 2, 50858 Koeln, Germany   +49 2234 1840-40  (fax)

  reply	other threads:[~2001-11-22 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 16:58 fs/exec.c and binfmt-xxx in 2.4.14 Heinz-Ado Arnolds
2001-11-21 17:08 ` Martin Dalecki
2001-11-21 17:31   ` Heinz-Ado Arnolds
2001-11-22 13:21   ` Colin Watson
2001-11-21 20:14 ` Andreas Ferber
2001-11-22 11:47   ` Heinz-Ado Arnolds [this message]
2001-11-22 12:43     ` Richard Guenther
2001-11-22 13:31     ` Andreas Schwab

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=3BFCE5BB.AD59B011@web-systems.net \
    --to=ado.arnolds@dhm-systems.de \
    --cc=aferber@techfak.uni-bielefeld.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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