From: David Laight <David.Laight@ACULAB.COM>
To: 'Borislav Petkov' <bp@alien8.de>, Theodore Ts'o <tytso@mit.edu>
Cc: X86 ML <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] x86: Remove a.out support
Date: Fri, 14 Jan 2022 09:51:19 +0000 [thread overview]
Message-ID: <4c76b01aee5c475a81fccf2fdfcb2080@AcuMS.aculab.com> (raw)
In-Reply-To: <YeCuNapJLK4M5sat@zn.tnic>
From: Borislav Petkov
> Sent: 13 January 2022 22:57
...
>
> Btw, pls do note that this is removing only the x86 a.out support -
> other arches (m68k and alpha) still select HAVE_AOUT and thus the
> respective glue in fs/binfmt_aout.c
I didn't think alpha was that old :-)
m68k is another matter.
But I've probably dismembered the only old m68k system disk I've had
to extract the magnets.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-01-14 9:51 UTC|newest]
Thread overview: 51+ 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 [this message]
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
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
2022-03-12 17:54 [PATCH] " 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
2022-04-04 18:18 ` Kees Cook
2022-04-04 8:24 ` Geert Uytterhoeven
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=4c76b01aee5c475a81fccf2fdfcb2080@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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).