From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by sourceware.org (Postfix) with ESMTPS id A47BA3857378 for ; Wed, 20 Apr 2022 16:51:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A47BA3857378 Received: by mail-pj1-x1030.google.com with SMTP id ll10so2447761pjb.5 for ; Wed, 20 Apr 2022 09:51:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=e9+En7kf8cMM4lilm6s+J9uWhGlWcAjQzxaK8L2b/yA=; b=pPVaoiqRLFA7oJWftW/RODVGl3AaSITsWZv/D00ZT56dWIo492/7uLNZYa5BYHPt20 ixevp03grfrtYKx+cBKEbmyNQMYIZqIpxhmkjxeQvj5E755zaWXRcjac1cxrDwPafoy2 koXkyi8C8Szy3hOVcV2VAfXTTOcRM/erKra1qSEesGZRxjMDZLjMtwT3yztzGZNhysCP p2QwPKmvyAk+E0beDS4NSlXLvH3I+uT5FPaWGiv8YKwLtV7ZcwuUKt3MZ5PB28TWRBX8 ujuLg3c3Q8nAGRjXJHnwqj576yZ+lx9oOcCbL0yi2DShNGDEaKUJD2p0q+0dW3v0xaj/ XuQw== X-Gm-Message-State: AOAM530wf3WyH8FsBL2iI5fu2tt6dOEJmbVgFNdDFHjgqganhdDsSYSh 37qxAoEjwysaXljdw1LoSYGEWg== X-Google-Smtp-Source: ABdhPJzHr7hb1CMb581iKLRjKcnWhaVG0GzBTLI6ORlSb6FQuuY7KCcKgljZRLw4A39xOXvmx3eGYQ== X-Received: by 2002:a17:90b:33cc:b0:1ce:a3fe:af41 with SMTP id lk12-20020a17090b33cc00b001cea3feaf41mr5502986pjb.229.1650473500753; Wed, 20 Apr 2022 09:51:40 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id e6-20020a056a001a8600b004fac74c8382sm21286448pfv.47.2022.04.20.09.51.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Apr 2022 09:51:40 -0700 (PDT) Date: Wed, 20 Apr 2022 09:51:39 -0700 From: Kees Cook To: will@kernel.org, broonie@kernel.org, catalin.marinas@arm.com Cc: linux-arm-kernel@lists.infradead.org, jeremy.linton@arm.com, hjl.tools@gmail.com, libc-alpha@sourceware.org, szabolcs.nagy@arm.com, yu-cheng.yu@intel.com, ebiederm@xmission.com, linux-arch@vger.kernel.org Subject: Re: [PATCH v13 0/2] arm64: Enable BTI for the executable as well as the interpreter Message-ID: <202204200951.68BC793FC3@keescook> References: <20220419105156.347168-1-broonie@kernel.org> <165043278356.1481705.13924459838445776007.b4-ty@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <165043278356.1481705.13924459838445776007.b4-ty@chromium.org> X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2022 16:51:42 -0000 On Tue, Apr 19, 2022 at 10:33:06PM -0700, Kees Cook wrote: > On Tue, 19 Apr 2022 11:51:54 +0100, Mark Brown wrote: > > Deployments of BTI on arm64 have run into issues interacting with > > systemd's MemoryDenyWriteExecute feature. Currently for dynamically > > linked executables the kernel will only handle architecture specific > > properties like BTI for the interpreter, the expectation is that the > > interpreter will then handle any properties on the main executable. > > For BTI this means remapping the executable segments PROT_EXEC | > > PROT_BTI. > > > > [...] > > Applied to for-next/execve, thanks! Now un-applied! :) -- Kees Cook