Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp1503954pxp; Thu, 10 Mar 2022 06:46:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJx1zpCoGFjyyqwA0Flgrb3X59XSCQYwXq32V+LvAV1FEAGajtqaFZb4SOIGdyaqJU68jLcD X-Received: by 2002:a17:902:ec8f:b0:152:939:ac45 with SMTP id x15-20020a170902ec8f00b001520939ac45mr5410604plg.61.1646923597551; Thu, 10 Mar 2022 06:46:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646923597; cv=none; d=google.com; s=arc-20160816; b=tTfEaDfp6OWeG6drx9MTVVeabDPcBFh/QHQulThnEJ+omp+vGp9N9qFjvt8IPuXWVL 61DLrhoSmYrf2lPUCIFLX6FW7kvjLTGfLY/WUtDKnFZzJXX8HuB+2npBAFAPSEuWxecw wAzPuNXH4kVwqjuLzOrNGBxusVTUUweuZA/I4Gc0NyHshBbN9+c6BSOa7ymqg1fSVwyv WplfXXrkqORFo9GAEV2KG6Hb/1+2OlJbUONlD83xsKc41vcFghDmmcKdeEk8xQG3Y1dz hsy3b342p6v8o2IQV2SLh3XJG6joayD0fvs0ylTgKeHiRE3f23R+0VnXEiLgpHbuyvXH WAMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:mime-version:user-agent:message-id :in-reply-to:date:references:cc:to:from; bh=jeI80UpzX3M9SRcnKiYT11098nuwU7EiXgJ6jLm1pdc=; b=VvnJmFFllLfWoyHnJV3oByvWuJyQ5Qr8hVkft/qhOM4ItitwOvKcnVeEww9itrHP4p mTDTXtxqK88rgDEpzj9lSbbPtbj1S+eac1TXDZDVdkb22KocUnBE6BN7i0cdntZ35ymo 2Wg4GY/OPZ97aTZ0QMe+rkDyQ93FkIihRD5mGesfWplX0/Qnhtt4VCpvOBu9hyfb40vL tgX5QPduDuV4m2R3Z1l4IIClV3qrzJcOQpYwloDwp8VNS6JqfX4reyi6Nc9WNZt35tAS MOqUaOfdhqlnJrqboD5oA2Sm8jUDx6TSlo/k9cclZsjDojWyB+UwbxHbrqSdx9a8FjFH O/dA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d3-20020a631d03000000b00364e8398936si4923725pgd.640.2022.03.10.06.46.21; Thu, 10 Mar 2022 06:46:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238083AbiCIUFd (ORCPT + 99 others); Wed, 9 Mar 2022 15:05:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236983AbiCIUFb (ORCPT ); Wed, 9 Mar 2022 15:05:31 -0500 Received: from out02.mta.xmission.com (out02.mta.xmission.com [166.70.13.232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2FB0D24BC3; Wed, 9 Mar 2022 12:04:31 -0800 (PST) Received: from in01.mta.xmission.com ([166.70.13.51]:38326) by out02.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1nS2Xh-00CxEg-Pi; Wed, 09 Mar 2022 13:04:17 -0700 Received: from ip68-227-174-4.om.om.cox.net ([68.227.174.4]:34642 helo=email.froward.int.ebiederm.org.xmission.com) by in01.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1nS2Xe-0012kW-1P; Wed, 09 Mar 2022 13:04:17 -0700 From: "Eric W. Biederman" To: Kees Cook Cc: John Paul Adrian Glaubitz , Borislav Petkov , Geert Uytterhoeven , Theodore Ts'o , X86 ML , Arnd Bergmann , LKML , Matt Turner , =?utf-8?Q?M=C3=A5ns_Rullg=C3=A5rd?= , Michael Cree , , Richard Henderson , Ivan Kokshaysky , Geert Uytterhoeven , linux-m68k@lists.linux-m68k.org, Linus Torvalds References: <20220113160115.5375-1-bp@alien8.de> Date: Wed, 09 Mar 2022 14:03:42 -0600 In-Reply-To: (John Paul Adrian Glaubitz's message of "Sat, 15 Jan 2022 20:42:59 +0100") Message-ID: <87ilsmdhb5.fsf_-_@email.froward.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1nS2Xe-0012kW-1P;;;mid=<87ilsmdhb5.fsf_-_@email.froward.int.ebiederm.org>;;;hst=in01.mta.xmission.com;;;ip=68.227.174.4;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1+e4yH+BUF7W62HMdvNWWMejYj/t+Qtgp8= X-SA-Exim-Connect-IP: 68.227.174.4 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-DCC: XMission; sa06 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: *;Kees Cook X-Spam-Relay-Country: X-Spam-Timing: total 3142 ms - load_scoreonly_sql: 0.04 (0.0%), signal_user_changed: 11 (0.3%), b_tie_ro: 9 (0.3%), parse: 0.97 (0.0%), extract_message_metadata: 22 (0.7%), get_uri_detail_list: 2.4 (0.1%), tests_pri_-1000: 25 (0.8%), tests_pri_-950: 1.24 (0.0%), tests_pri_-900: 1.02 (0.0%), tests_pri_-90: 91 (2.9%), check_bayes: 89 (2.8%), b_tokenize: 10 (0.3%), b_tok_get_all: 9 (0.3%), b_comp_prob: 2.4 (0.1%), b_tok_touch_all: 64 (2.0%), b_finish: 0.95 (0.0%), tests_pri_0: 1994 (63.4%), check_dkim_signature: 0.52 (0.0%), check_dkim_adsp: 3.8 (0.1%), poll_dns_idle: 977 (31.1%), tests_pri_10: 3.1 (0.1%), tests_pri_500: 991 (31.5%), rewrite_mail: 0.00 (0.0%) Subject: [PATCH] a.out: Stop building a.out/osf1 support on alpha and m68k X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There has been repeated discussion on removing a.out support, the most recent was[1]. Having read through a bunch of the discussion it looks like no one has see any reason why we need to keep a.out support. The m68k maintainer has even come out in favor of removing a.out support[2]. At a practical level with only two rarely used architectures building a.out support, it gets increasingly hard to test and to care about. Which means the code will almost certainly bit-rot. Let's see if anyone cares about a.out support on the last two architectures that build it, by disabling the build of the support in Kconfig. If anyone cares, this can be easily reverted, and we can then have a discussion about what it is going to take to support a.out binaries in the long term. Cc: Richard Henderson Cc: Ivan Kokshaysky Cc: Matt Turner Cc: linux-alpha@vger.kernel.org Cc: Geert Uytterhoeven Cc: linux-m68k@lists.linux-m68k.org [1] https://lkml.kernel.org/r/20220113160115.5375-1-bp@alien8.de [2] https://lkml.kernel.org/r/CAMuHMdUbTNNr16YY1TFe=-uRLjg6yGzgw_RqtAFpyhnOMM5Pvw@mail.gmail.com Signed-off-by: "Eric W. Biederman" --- Kees do you think you could add this to your execve branch? I think this should be a complimentary patch to Borislav Petkov's patch at the top of this tread to remove a.out support on x86. arch/alpha/Kconfig | 1 - arch/m68k/Kconfig | 1 - 2 files changed, 2 deletions(-) diff --git a/arch/alpha/Kconfig b/arch/alpha/Kconfig index 4e87783c90ad..14c97acea351 100644 --- a/arch/alpha/Kconfig +++ b/arch/alpha/Kconfig @@ -12,7 +12,6 @@ config ALPHA select FORCE_PCI if !ALPHA_JENSEN select PCI_DOMAINS if PCI select PCI_SYSCALL if PCI - select HAVE_AOUT select HAVE_ASM_MODVERSIONS select HAVE_PCSPKR_PLATFORM select HAVE_PERF_EVENTS diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig index 936e1803c7c7..268b3860d40d 100644 --- a/arch/m68k/Kconfig +++ b/arch/m68k/Kconfig @@ -17,7 +17,6 @@ config M68K select GENERIC_CPU_DEVICES select GENERIC_IOMAP select GENERIC_IRQ_SHOW - select HAVE_AOUT if MMU select HAVE_ASM_MODVERSIONS select HAVE_DEBUG_BUGVERBOSE select HAVE_EFFICIENT_UNALIGNED_ACCESS if !CPU_HAS_NO_UNALIGNED -- 2.29.2