From: Richard Weinberger <richard@nod.at>
To: Borislav Petkov <bp@alien8.de>
Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Jann Horn <jannh@google.com>, Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
kernel list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH] x86: Deprecate a.out support
Date: Tue, 05 Mar 2019 16:17:35 +0100 [thread overview]
Message-ID: <9780784.9EOYMQBb1X@blindfold> (raw)
In-Reply-To: <20190305145717.GD8256@zn.tnic>
Am Dienstag, 5. März 2019, 15:59:52 CET schrieb Borislav Petkov:
> + akpm and Linus.
>
> On Tue, Mar 05, 2019 at 01:43:47PM +0000, Alan Cox wrote:
> > > It's been 25 years since Linux added support for ELF. Can we just
> > > delete the a.out support entirely now? According to the Linux-ELF HOWTO,
> > > support was added in 1.1.52 (August 1994). It's pretty much necromancy
> > > at this point.
> >
> > In the unlikely event that someone actually has an a.out binary they
> > can't live with they can also just write an a.out loader as an ELF
> > program entirely in userspace.
> >
> > I'd vote for giving it the boot unless there are any architectures that
> > kept using a.out far longer due to tool chain issues ?
>
> We can at least deprecate it on x86...
>
> ---
> From: Borislav Petkov <bp@suse.de>
> Date: Tue, 5 Mar 2019 15:47:51 +0100
> Subject: [PATCH] x86: Deprecate a.out support
>
> Linux supports ELF binaries for ~25 years now. a.out coredumping has
> bitrotten quite significantly and would need some fixing to get it into
> shape again but considering how even the toolchains cannot create a.out
> executables in its default configuration, let's deprecate a.out support
> and remove it a couple of releases later, instead.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
> Cc: Jann Horn <jannh@google.com>
> Cc: <linux-api@vger.kernel.org>
> Cc: <linux-fsdevel@vger.kernel.org>
> Cc: lkml <linux-kernel@vger.kernel.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: <x86@kernel.org>
> ---
> arch/x86/Kconfig | 2 +-
> arch/x86/um/Kconfig | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 68261430fe6e..ade12ec4224b 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -14,7 +14,6 @@ config X86_32
> select ARCH_WANT_IPC_PARSE_VERSION
> select CLKSRC_I8253
> select CLONE_BACKWARDS
> - select HAVE_AOUT
> select HAVE_GENERIC_DMA_COHERENT
> select MODULES_USE_ELF_REL
> select OLD_SIGACTION
> @@ -2843,6 +2842,7 @@ config IA32_EMULATION
> config IA32_AOUT
> tristate "IA32 a.out support"
> depends on IA32_EMULATION
> + depends on BROKEN
> ---help---
> Support old a.out binaries in the 32bit emulation.
>
> diff --git a/arch/x86/um/Kconfig b/arch/x86/um/Kconfig
> index f518b4744ff8..494eeb51e4e1 100644
> --- a/arch/x86/um/Kconfig
> +++ b/arch/x86/um/Kconfig
> @@ -16,7 +16,6 @@ config 64BIT
>
> config X86_32
> def_bool !64BIT
> - select HAVE_AOUT
> select ARCH_WANT_IPC_PARSE_VERSION
> select MODULES_USE_ELF_REL
> select CLONE_BACKWARDS
>
For UML,
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
next prev parent reply other threads:[~2019-03-05 15:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 23:57 a.out coredumping: fix or delete? Jann Horn
2019-03-03 1:09 ` Andy Lutomirski
2019-03-05 9:19 ` Borislav Petkov
2019-03-05 12:22 ` Matthew Wilcox
2019-03-05 13:43 ` Alan Cox
2019-03-05 14:59 ` [PATCH] x86: Deprecate a.out support Borislav Petkov
2019-03-05 15:17 ` Richard Weinberger [this message]
2019-03-05 16:22 ` Linus Torvalds
2019-03-05 16:30 ` Jann Horn
2019-03-05 17:32 ` Borislav Petkov
2019-03-05 17:31 ` Borislav Petkov
2019-03-05 17:58 ` Linus Torvalds
2019-03-05 18:11 ` Borislav Petkov
2019-03-05 18:18 ` Borislav Petkov
2019-03-06 15:07 ` Geert Uytterhoeven
2019-03-10 21:37 ` Matt Turner
2019-03-10 22:40 ` Linus Torvalds
2019-03-10 23:19 ` Al Viro
2019-03-11 7:20 ` John Paul Adrian Glaubitz
2019-03-11 11:02 ` Arnd Bergmann
2019-03-11 16:26 ` Måns Rullgård
2019-03-11 16:45 ` Linus Torvalds
2019-03-11 18:08 ` Måns Rullgård
2019-03-11 19:03 ` Linus Torvalds
2019-03-11 19:47 ` Måns Rullgård
2019-03-11 20:50 ` Matt Turner
2019-03-11 21:34 ` Arnd Bergmann
2019-03-11 21:45 ` Linus Torvalds
2019-03-11 22:12 ` Måns Rullgård
2019-03-12 8:44 ` Geert Uytterhoeven
2019-03-14 18:38 ` Miguel Ojeda
2019-03-11 22:06 ` Måns Rullgård
2019-03-11 22:11 ` Matt Turner
2019-03-12 6:38 ` Michael Cree
2019-04-16 3:19 ` Jon Masters
2019-03-11 18:58 ` Matt Turner
2019-03-06 16:55 ` Enrico Weigelt, metux IT consult
2019-03-06 17:52 ` [PATCH] fs: binfmt: mark aout as broken Enrico Weigelt, metux IT consult
2019-03-06 12:25 ` a.out coredumping: fix or delete? Thomas Gleixner
2019-03-06 14:11 ` Theodore Y. Ts'o
2019-03-06 16:52 ` Alan Cox
2019-03-06 17:45 ` Andy Lutomirski
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=9780784.9EOYMQBb1X@blindfold \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--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).