From: Linus Torvalds <torvalds@linux-foundation.org>
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 <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>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH] x86: Deprecate a.out support
Date: Tue, 5 Mar 2019 09:58:28 -0800 [thread overview]
Message-ID: <CAHk-=wg0bY=RFhD4NW9x++fC0bME=_-9xM3kexGGM3gefHQTyQ@mail.gmail.com> (raw)
In-Reply-To: <20190305173134.GE8256@zn.tnic>
On Tue, Mar 5, 2019 at 9:31 AM Borislav Petkov <bp@alien8.de> wrote:
>
> So how do you wanna handle this?
>
> I guess the easiest would be if you apply your patch directly now and
> add the a.out phase-out strategy we're going for in its commit message
> so that people are aware of what we're doing.
Yup, I'll just do that. I'll fix up my patch to be more complete (ie
the a.out-core.h removal Jann pointed out).
I'll talk about removing a.out support entirely in the commit message.
I'd be ok for that to be a total removal, but maybe there are some
architectures that still have that as a "main" format?
Or I could just apply your patch after removing the core-dumping. Comments?
Linus
next prev parent reply other threads:[~2019-03-05 17:58 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
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 [this message]
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='CAHk-=wg0bY=RFhD4NW9x++fC0bME=_-9xM3kexGGM3gefHQTyQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--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=richard@nod.at \
--cc=tglx@linutronix.de \
--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).