From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Borislav Petkov" <bp@alien8.de>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Theodore Ts'o" <tytso@mit.edu>, "X86 ML" <x86@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
"Matt Turner" <mattst88@gmail.com>,
"Måns Rullgård" <mans@mansr.com>,
"Michael Cree" <mcree@orcon.net.nz>,
linux-arch <linux-arch@vger.kernel.org>,
"Richard Henderson" <rth@twiddle.net>,
"Ivan Kokshaysky" <ink@jurassic.park.msu.ru>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k
Date: Wed, 9 Mar 2022 14:02:42 -0800 [thread overview]
Message-ID: <202203091358.775E158C@keescook> (raw)
In-Reply-To: <CAHk-=wg+TYsns5JvNds6BVG7ezdg8uM_z9m8uJBcRDANdd7csw@mail.gmail.com>
On Wed, Mar 09, 2022 at 12:37:54PM -0800, Linus Torvalds wrote:
> On Wed, Mar 9, 2022 at 12:04 PM Eric W. Biederman <ebiederm@xmission.com> wrote:
> >
> > Let's see if anyone cares about a.out support on the last two
> > architectures that build it, by disabling the build of the support in
> > Kconfig.
> [...]
> But sure, it would be interesting to know if any alpha people care - I
> just have this suspicion that we can't drop it that easily because of
> the non-Linux legacy.
It looks like the only distro supporting Alpha is Gentoo. I pulled
down the installation media, and everything is ELF except for firmware
COFF files:
$ find . -type f | xargs file | grep -Ei ':.*(out|coff)'
./lib/firmware/meson/vdec/g12a_hevc_mmu.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/meson/vdec/g12a_vp9.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/meson/vdec/gxl_hevc_mmu.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/meson/vdec/gxl_vp9.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/meson/vdec/sm1_hevc_mmu.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/meson/vdec/sm1_vp9_mmu.bin: MIPSEB MIPS-III ECOFF executable not stripped - version 0.0
./lib/firmware/qca/crbtfw32.tlv: mc68k COFF object not stripped
So, since it's an easy revert, sure. Let's do it.
--
Kees Cook
next prev parent reply other threads:[~2022-03-09 22:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:01 [PATCH] x86: Remove a.out support 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 20:37 ` Linus Torvalds
2022-03-09 22:02 ` Kees Cook [this message]
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-03-10 8:09 ` [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k Geert Uytterhoeven
2022-01-15 4:54 ` [PATCH] x86: Remove a.out support David Laight
2022-03-11 14:40 ` [tip: x86/cleanups] " tip-bot2 for Borislav Petkov
2022-04-11 17:42 ` tip-bot2 for Borislav Petkov
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=202203091358.775E158C@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mans@mansr.com \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=rth@twiddle.net \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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).