lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 Mar 2019 09:58:28 -0800 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Borislav Petkov <bp@...en8.de> Cc: Alan Cox <gnomes@...rguk.ukuu.org.uk>, Matthew Wilcox <willy@...radead.org>, Jann Horn <jannh@...gle.com>, Al Viro <viro@...iv.linux.org.uk>, Thomas Gleixner <tglx@...utronix.de>, kernel list <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, "the arch/x86 maintainers" <x86@...nel.org>, Linux API <linux-api@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Richard Weinberger <richard@....at>, Anton Ivanov <anton.ivanov@...bridgegreys.com> Subject: Re: [PATCH] x86: Deprecate a.out support On Tue, Mar 5, 2019 at 9:31 AM Borislav Petkov <bp@...en8.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
Powered by blists - more mailing lists