can't find file to patch at input line 108 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From patchwork Fri Jun 4 11:24:49 2021 |Content-Type: text/plain; charset="utf-8" |MIME-Version: 1.0 |Content-Transfer-Encoding: 7bit |X-Patchwork-Submitter: Mark Brown |X-Patchwork-Id: 43724 |Return-Path: |X-Original-To: patchwork@sourceware.org |Delivered-To: patchwork@sourceware.org |Received: from server2.sourceware.org (localhost [IPv6:::1]) | by sourceware.org (Postfix) with ESMTP id 01C5D399A86A | for ; Fri, 4 Jun 2021 11:27:46 +0000 (GMT) |DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 01C5D399A86A |DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; | s=default; t=1622806066; | bh=XHjZqU18z3nrmyx5yE8KXAGFGEzK2mBz/9N3glepKHI=; | h=To:Subject:Date:In-Reply-To:References:List-Id:List-Unsubscribe: | List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: | From; | b=ZLLTPNr22cIXPdXOVPC0AEX55FfbBDdhQJV8BiyysR5pvB3TPgsp69vz6qycNfFmh | frZyCCN2iykuZeehjbftdda9i5zMIIWKTbcfq30S8XtJY2AWcqSEf5G8VBE2dETiSw | NVrsMn+mQM02F34IAhV+qZNhs03gky7XiqW9VIvc= |X-Original-To: libc-alpha@sourceware.org |Delivered-To: libc-alpha@sourceware.org |Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) | by sourceware.org (Postfix) with ESMTPS id 1AAA1399A87E | for ; Fri, 4 Jun 2021 11:25:10 +0000 (GMT) |DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1AAA1399A87E |Received: by mail.kernel.org (Postfix) with ESMTPSA id AFAAF613AC; | Fri, 4 Jun 2021 11:25:08 +0000 (UTC) |To: Catalin Marinas , | Will Deacon |Subject: [PATCH v2 2/3] arm64: Enable BTI for main executable as well as the | interpreter |Date: Fri, 4 Jun 2021 12:24:49 +0100 |Message-Id: <20210604112450.13344-3-broonie@kernel.org> |X-Mailer: git-send-email 2.20.1 |In-Reply-To: <20210604112450.13344-1-broonie@kernel.org> |References: <20210604112450.13344-1-broonie@kernel.org> |MIME-Version: 1.0 |X-Developer-Signature: v=1; a=openpgp-sha256; l=3182; h=from:subject; | bh=YIMcXq5zjPTU6TnWkCaebLW4hx7QitAn2BiMS6aUhsU=; | b=owEBbQGS/pANAwAKASTWi3JdVIfQAcsmYgBgug2Ad6SBiufM2R00KzOUZstotWdq3dPQbkCl/0c/ | dJZN8kGJATMEAAEKAB0WIQSt5miqZ1cYtZ/in+ok1otyXVSH0AUCYLoNgAAKCRAk1otyXVSH0P7/B/ | 4tCAwJjnNQXw/27zkcreggBq81xCwXUMkmhe5Da0t2hlVLMTzHUZa5PhTW/xbFgwZ2BmI99tWGhWq1 | pRE6tZX/zV980453w2zG4n8Qsn5elye5GzCBVKIqMxzceVRSoiJJAZzI/mtayz0yVxmvooXchICfwo | 8Wtb20YOQ/DgbucYrsI6/202fuNW09UlE5Qv6fL76SY0g7vysbyHItn8ewwFSUX+X8otZAAVVam76g | rm0vHF0TaYaOtf8opVavaReEWX7BLFGr6taLJ6POefjwh3IuJtR7AdXvhoWTPhAampeepr4s5DwmtW | FVATyU00PRaOWSwKpNgRE1Qmfi9orJ |X-Developer-Key: i=broonie@kernel.org; a=openpgp; | fpr=3F2568AAC26998F9E813A1C5C3F436CA30F5D8EB |X-Spam-Status: No, score=-10.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, | DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, | SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 |X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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-Patchwork-Original-From: Mark Brown via Libc-alpha | |From: Mark Brown |Reply-To: Mark Brown |Cc: linux-arch@vger.kernel.org, Yu-cheng Yu , | libc-alpha@sourceware.org, Szabolcs Nagy , | Jeremy Linton , Mark Brown , | Dave Martin , linux-arm-kernel@lists.infradead.org |Errors-To: libc-alpha-bounces+patchwork=sourceware.org@sourceware.org |Sender: "Libc-alpha" | | |Currently for dynamically linked ELF executables we only enable BTI for |the interpreter, expecting the interpreter to do this for the main |executable. This is a bit inconsistent since we do map main executable and |is causing issues with systemd's MemoryDenyWriteExecute feature which is |implemented using a seccomp filter which prevents setting PROT_EXEC on |already mapped memory and lacks the context to be able to detect that |memory is already mapped with PROT_EXEC. | |Resolve this by checking the BTI property for the main executable and |enabling BTI if it is present when doing the initial mapping. This does |mean that we may get more code with BTI enabled if running on a system |without BTI support in the dynamic linker, this is expected to be a safe |configuration and testing seems to confirm that. It also reduces the |flexibility userspace has to disable BTI but it is expected that for cases |where there are problems which require BTI to be disabled it is more likely |that it will need to be disabled on a system level. | |Signed-off-by: Mark Brown |Reviewed-by: Dave Martin |--- | arch/arm64/include/asm/elf.h | 14 ++++++++++---- | arch/arm64/kernel/process.c | 18 ++++++------------ | 2 files changed, 16 insertions(+), 16 deletions(-) | |diff --git a/arch/arm64/include/asm/elf.h b/arch/arm64/include/asm/elf.h |index a488a1329b16..9f86dbce2680 100644 |--- a/arch/arm64/include/asm/elf.h |+++ b/arch/arm64/include/asm/elf.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 140 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c |index b4bb67f17a2c..f7fff4a4c99f 100644 |--- a/arch/arm64/kernel/process.c |+++ b/arch/arm64/kernel/process.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored