From: Kees Cook <keescook@chromium.org>
To: James Jones <linux@theinnocuous.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@alien8.de>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Remove a.out support
Date: Thu, 17 Mar 2022 11:53:19 -0700 [thread overview]
Message-ID: <202203171152.F35EB19767@keescook> (raw)
In-Reply-To: <59fb3d14-423a-d39b-04cb-1e60ee67d3f1@theinnocuous.com>
On Thu, Mar 17, 2022 at 02:04:46AM +0000, James Jones wrote:
> On 3/16/22 3:30 PM, Kees Cook wrote:
> > On Wed, Mar 16, 2022 at 01:38:31PM +0100, Arnd Bergmann wrote:
> >> is in the end, but it's likely easier than a standalone a.out loader
> >> in user space, or a conversion to ELF format.
> >
> > Yeah, the exec format is really simple. The only tricky bit was preparing
> > the stack and making sure everything landed in the right place for text
> > and data. James, can you try this? aln and mac run for me, but I'm not
> > actually exercising them beyond dumping argument lists, etc:
> >
> > https://github.com/kees/kernel-tools/tree/trunk/a.out
>
> Yes, works perfectly, thank you. I like the idea of using this much
Hurray!
> better than getting emailed every time someone wants to delete the a.out
> code again. Consider my use case withdrawn. I've already pushed an
> update to my jaguar-sdk project to use this tool instead.
Nice; I see there are other binaries besides aln and mac that are
working with this too? *whew* I'm glad it was relatively straight
forward. :)
--
Kees Cook
next prev parent reply other threads:[~2022-03-17 18:53 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 [this message]
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
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=202203171152.F35EB19767@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@theinnocuous.com \
--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).