From: David Laight <David.Laight@ACULAB.COM>
To: "'Maciej W. Rozycki'" <macro@orcam.me.uk>,
Kees Cook <keescook@chromium.org>
Cc: James Jones <linux@theinnocuous.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] x86: Remove a.out support
Date: Mon, 4 Apr 2022 17:07:11 +0000 [thread overview]
Message-ID: <08c095230941445f9139ab89bc70da43@AcuMS.aculab.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2204041135210.47162@angie.orcam.me.uk>
From: Maciej W. Rozycki
> Sent: 04 April 2022 12:04
>
> On Sat, 2 Apr 2022, Kees Cook wrote:
>
> > > Chiming in late as I'm scanning outstanding mailing list traffic: if this
> > >is as you say all statically linked stuff, then converting from a.out to
> > >ELF might be as easy as:
> > >
> > >$ objcopy -I a.out-i386-linux -O elf32-i386 a.out-binary elf-binary
> >
> > Based on my research (and the wrapper I ended up writing), I don't think
> > this is sufficient because entry point handling is different between ELF
> > and a.out (specifically the stack layout and initial sp register value).
>
> Fair enough. I guess the exact value of %esp doesn't matter that much
> (why would it?), but the arguments and environment may well be structured
> differently (and indeed based on a glance over binfmt_aout.c there's extra
> indirection involved compared to the ELF i386 psABI).
You could write a custom 'elf interpreter'.
Hacking at those isn't for the faint-hearted :-)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-04-04 21:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 17:54 [PATCH] x86: Remove a.out support James Jones
2022-03-12 18:06 ` James Jones
2022-03-13 11:56 ` Borislav Petkov
2022-03-13 18:26 ` James Jones
2022-03-15 9:44 ` Borislav Petkov
2022-03-15 19:51 ` Kees Cook
2022-03-16 5:06 ` James Jones
2022-03-16 12:38 ` Arnd Bergmann
2022-03-16 22:30 ` Kees Cook
2022-03-17 2:04 ` James Jones
2022-03-17 2:08 ` David Laight
2022-03-17 10:17 ` Borislav Petkov
2022-03-17 18:53 ` Kees Cook
2022-03-17 2:32 ` David Laight
2022-03-17 3:22 ` Kees Cook
2022-03-16 16:10 ` Kees Cook
2022-03-16 17:05 ` David Laight
2022-04-02 22:14 ` Maciej W. Rozycki
2022-04-03 2:24 ` Kees Cook
2022-04-04 11:03 ` Maciej W. Rozycki
2022-04-04 17:07 ` David Laight [this message]
2022-04-04 18:18 ` Kees Cook
2022-04-04 8:24 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2022-01-13 16:01 Borislav Petkov
2022-01-13 18:08 ` Kees Cook
2022-01-13 18:47 ` Theodore Ts'o
2022-01-13 22:56 ` Borislav Petkov
2022-01-14 4:06 ` Theodore Ts'o
2022-01-14 10:40 ` Arnd Bergmann
2022-01-14 19:09 ` Borislav Petkov
2022-01-14 9:51 ` David Laight
2022-01-14 14:52 ` Geert Uytterhoeven
2022-01-14 18:57 ` Theodore Ts'o
2022-01-14 19:00 ` Geert Uytterhoeven
2022-01-14 19:12 ` Borislav Petkov
2022-01-14 19:21 ` Geert Uytterhoeven
2022-01-14 19:35 ` Borislav Petkov
2022-01-15 11:37 ` Borislav Petkov
2022-01-15 19:42 ` John Paul Adrian Glaubitz
2022-03-09 20:03 ` [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k Eric W. Biederman
2022-03-09 22:04 ` Kees Cook
2022-03-10 23:29 ` [PATCH] x86: Remove a.out support Eric W. Biederman
2022-03-10 23:35 ` Linus Torvalds
2022-03-11 8:47 ` Arnd Bergmann
2022-03-11 10:03 ` Borislav Petkov
2022-01-15 4:54 ` David Laight
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=08c095230941445f9139ab89bc70da43@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bp@alien8.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@theinnocuous.com \
--cc=macro@orcam.me.uk \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).