From: Borislav Petkov <bp@alien8.de>
To: Jann Horn <jannh@google.com>
Cc: 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>
Subject: Re: a.out coredumping: fix or delete?
Date: Tue, 5 Mar 2019 10:19:04 +0100 [thread overview]
Message-ID: <20190305091904.GB8256@zn.tnic> (raw)
In-Reply-To: <CAG48ez1RVd5mQ_Pb6eygQESaZhpQz765OAZYSoPE0kPqfZEXQg@mail.gmail.com>
On Sat, Mar 02, 2019 at 12:57:30AM +0100, Jann Horn wrote:
> In theory, Linux can dump cores for a.out binaries. In practice, that
> code is pretty bitrotten and buggy. Does anyone want that code so much
> that they'd like to fix it, or can we just delete it?
I was asking myself the same question while doing
10970e1b4be9 ("x86/a.out: Clear the dump structure initially")
especially since it is kinda hard to get the toolchain to even create an
a.out executable - your script to create one case-in-point.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-03-05 9:19 UTC|newest]
Thread overview: 52+ 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 [this message]
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
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:26 ` Måns Rullgård
2019-03-11 16:45 ` Linus Torvalds
2019-03-11 18:08 ` Måns Rullgård
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 19:47 ` Måns Rullgård
2019-03-11 20:50 ` Matt Turner
2019-03-11 20:50 ` Matt Turner
2019-03-11 21:34 ` Arnd Bergmann
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-11 22:12 ` Måns Rullgård
2019-03-12 8:44 ` Geert Uytterhoeven
2019-03-14 18:38 ` Miguel Ojeda
2019-03-14 18:38 ` Miguel Ojeda
2019-03-11 22:06 ` Måns Rullgård
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 14:11 ` Theodore Y. Ts'o
2019-03-06 16:52 ` Alan Cox
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=20190305091904.GB8256@zn.tnic \
--to=bp@alien8.de \
--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=viro@zeniv.linux.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.