From: Heinz-Ado Arnolds <Ado.Arnolds@dhm-systems.de>
To: dalecki@evision.ag
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: fs/exec.c and binfmt-xxx in 2.4.14
Date: Wed, 21 Nov 2001 18:31:08 +0100 [thread overview]
Message-ID: <3BFBE4DB.44D9ACCF@web-systems.net> (raw)
In-Reply-To: <3BFBDD32.434AB47B@web-systems.net> <3BFBDFA5.DDA1CC98@evision-ventures.com>
Martin Dalecki wrote:
>
> Heinz-Ado Arnolds wrote:
> >
> > Hi Linus, Hi Alan, Hi all,
> >
> > I have a problem with loading modules for binary formats. The
> > reason for this problem shows up in fs/exec.c search_binary_handler().
> >
> > Starting with linux-2.1.23 (and up to 2.4.14) there was a change
> > in the format and offset of printing the magic number for requesting
> > a handler module. Up to 2.1.22 the statement
>
> That is a time span of several years during which nobody realized
> there was a problem with this. Therefore I would rather
> request for removal of the whole binfmt-misc stuff (which is ugly
> anyway)
> rather then "fixing it" ;-)
Not really. I asked for this problem back in 1999 but didn't get any
satisfying response. Since that time me and a lot of my friends are
applying this patch to every new kernel we install. For me and many
other the binfmt interface is a great tool and by far not ugly stuff.
--
------------------------------------------------------------------------
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)
next prev parent reply other threads:[~2001-11-21 17:31 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 [this message]
2001-11-22 13:21 ` Colin Watson
2001-11-21 20:14 ` Andreas Ferber
2001-11-22 11:47 ` Heinz-Ado Arnolds
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=3BFBE4DB.44D9ACCF@web-systems.net \
--to=ado.arnolds@dhm-systems.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dalecki@evision.ag \
--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