From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 08E22C43381 for ; Tue, 5 Mar 2019 18:11:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CDA4020848 for ; Tue, 5 Mar 2019 18:11:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="hWuY5K7E" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728325AbfCESLo (ORCPT ); Tue, 5 Mar 2019 13:11:44 -0500 Received: from mail.skyhub.de ([5.9.137.197]:45370 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726100AbfCESLn (ORCPT ); Tue, 5 Mar 2019 13:11:43 -0500 Received: from zn.tnic (p200300EC2BCD6B00ECFD1928E9AB0C1D.dip0.t-ipconnect.de [IPv6:2003:ec:2bcd:6b00:ecfd:1928:e9ab:c1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id B324A1EC014B; Tue, 5 Mar 2019 19:11:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1551809501; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=rk2EqGQJGFUxRIyLK5y963XceUK24qDSS4tj8E8Lhlw=; b=hWuY5K7Edb1hBrZq7M2J6UL1AEIBruacvjEa22Hh9BNbFCl7ionvBaf2/iAWeY+GymdiBZ mZuOuZjnM2C3xYT/RaDaB8g8EHlvsLKzQk0/AUF3877Y8D/BVhm9B3T/WlVQ3oOJKu7s9M zuueTqYVns4cXYeCSD9QqK6o39LvDKU= Date: Tue, 5 Mar 2019 19:11:38 +0100 From: Borislav Petkov To: Linus Torvalds Cc: Alan Cox , Matthew Wilcox , Jann Horn , Al Viro , Thomas Gleixner , kernel list , linux-fsdevel , the arch/x86 maintainers , Linux API , Andrew Morton , Richard Weinberger , Anton Ivanov Subject: Re: [PATCH] x86: Deprecate a.out support Message-ID: <20190305181138.GG8256@zn.tnic> References: <20190305091904.GB8256@zn.tnic> <20190305122218.GD13380@bombadil.infradead.org> <20190305134347.4be2449c@alans-desktop> <20190305145717.GD8256@zn.tnic> <20190305173134.GE8256@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 05, 2019 at 09:58:28AM -0800, Linus Torvalds wrote: > 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? Well, my limited experience with feature removal says that people only say something when the feature is *actually* long gone, several releases have passed by and the removal has finally percolated downstream. I guess you could Cc arch maintainers with the a.out-core.h removal patch to see if anyone screams. > Or I could just apply your patch after removing the core-dumping. Comments? Sure. And it can be reverted very easily if someone runs out of the woods later and handwaving about an important a.out use case on x86. Although x86 should be in ELF-land for a quarter of a decade now. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.