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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4BC05CDB482 for ; Wed, 18 Oct 2023 12:28:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/Srasw3WYL/6T2HGfRu/F40m8tlKaUtDyt9J+eiduE0=; b=4xjRwDVz922/ln sBZ9gjl9L3BP7mbuo5qjsql8JAvgeV0RplAY1jrBsU4Gy32tdiT01S5BO0/vCBxclNdiLu7XfnduG k7f+0y68KFCtaGoas2u3n1w5b4yt3Ka5kuEdl/rzTp0gOBvh8gJNDEG9hu+L/HcL1SaR5Xf5wZNxX W1Yne0bRvV2ecnBuytnTDZiNAahlu/pvIm/Kot0EssVLD299ZzaQ4HMKUkUjX8vaKiGsCHlQjYaQC i1fjh5XWMlxxIq+aq/L+L1Y6PCD8jWg3H5XLWMregbmhDbeyydwdwmpsUqRpUcufgyTpHZ1k+V0za 49OrUID5kUqafLgtCPGw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qt5eK-00EeuK-1o; Wed, 18 Oct 2023 12:27:44 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qt5eH-00EerS-0d for linux-arm-kernel@lists.infradead.org; Wed, 18 Oct 2023 12:27:42 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 5B3B8CE24B8; Wed, 18 Oct 2023 12:27:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 25D30C433C8; Wed, 18 Oct 2023 12:27:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697632055; bh=3oMHWPgTZG+wzUE1L2j7bPKf+yDdpXrGoQcpak/VDrs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gsIVjBfchCmuA+zAYWvguw/d9o+Nn5OfO435koR3kW6NsDUccc/np1OVblibxiCCP gkCD6jYmh2VnrNbFuB8qXkX+Kv/MmCIvP11/d76Px8N4CcMsG0VNS2SHpfqCRcYkoz 5l/lPhHiYbruGVg/bnlscThapy+Zv0UeJQNqw/fkYYyoq+ZijaK3E7hmJ5KQ/Anxl+ dn4gj8Q2f5ztj5HTeDkKZ6zSnvo9P3SDaTWMak4LxKcjR79KiwzbqPGwoC7hArpK32 pmLaxY0TtbLQtMNSYq/N3thH1HAEwQBc2Ys66sjwKAtULBvIBEdnO31w1Ji33KaQo0 Sdtugu2J3X6bA== Date: Wed, 18 Oct 2023 13:27:30 +0100 From: Will Deacon To: Andrea della Porta Cc: Catalin Marinas , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, nik.borisov@suse.com, arnd@arndb.de, keescook@chromium.org Subject: Re: [PATCH 0/4] arm64: Make Aarch32 compatibility enablement optional at boot Message-ID: <20231018122729.GA18556@willie-the-truck> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231018_052741_405709_505DB799 X-CRM114-Status: GOOD ( 11.20 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, On Wed, Oct 18, 2023 at 01:13:18PM +0200, Andrea della Porta wrote: > Aarch32 compatibility mode is enabled at compile time through > CONFIG_COMPAT Kconfig option. This patchset lets 32-bit support > (for both processes and syscalls) be enabled at boot time using > a kernel parameter. Also, it provides a mean for distributions > to set their own default without sacrificing compatibility support, > that is users can override default behaviour through the kernel > parameter. I proposed something similar in the past: https://lkml.kernel.org/linux-fsdevel/20210916131816.8841-1-will@kernel.org/ bu the conclusion there (see the reply from Kees) was that it was better to either use existing seccomp mechanisms or add something to control which binfmts can be loaded. Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel