can't find file to patch at input line 109 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From patchwork Mon Jul 19 16:45:34 2021 |Content-Type: text/plain; charset="utf-8" |MIME-Version: 1.0 |Content-Transfer-Encoding: 7bit |X-Patchwork-Submitter: Mark Brown |X-Patchwork-Id: 44410 |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 71BEA395BC1B | for ; Mon, 19 Jul 2021 16:47:59 +0000 (GMT) |DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 71BEA395BC1B |DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; | s=default; t=1626713279; | bh=LXBowOkBp3Q2jqqF35GJf2KzxMorztV7KFuefEhl/dg=; | 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=CxPpa97S80dsAIag5puiafpCFnCPklhfXc9RB0rLrtqqrUknch9WVbP5FKnEaAweD | RCBPoSPR4fGwWNsPQUGju3iQNv6Q8NVcBWSGQelnWtxNTSjEwXNofNZfC90Qh/XKvl | 6VSQov9y8H4aLRa0E+T4iVNPWkQc2OunLTsQMapM= |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 B4E77395C038 | for ; Mon, 19 Jul 2021 16:46:15 +0000 (GMT) |DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B4E77395C038 |Received: by mail.kernel.org (Postfix) with ESMTPSA id DD5DD61221; | Mon, 19 Jul 2021 16:46:13 +0000 (UTC) |To: Catalin Marinas , | Will Deacon |Subject: [PATCH v5 2/4] arm64: Enable BTI for main executable as well as the | interpreter |Date: Mon, 19 Jul 2021 17:45:34 +0100 |Message-Id: <20210719164536.19143-3-broonie@kernel.org> |X-Mailer: git-send-email 2.20.1 |In-Reply-To: <20210719164536.19143-1-broonie@kernel.org> |References: <20210719164536.19143-1-broonie@kernel.org> |MIME-Version: 1.0 |X-Developer-Signature: v=1; a=openpgp-sha256; l=3271; h=from:subject; | bh=CO++giUYoHXNfg+ZM1q/9xAugE5bMJJQr1XwojyQrKg=; | b=owEBbQGS/pANAwAKASTWi3JdVIfQAcsmYgBg9awtaL5taIcuRXN131n30QOb5aon69WBKpFrMP8R | NHv0qSmJATMEAAEKAB0WIQSt5miqZ1cYtZ/in+ok1otyXVSH0AUCYPWsLQAKCRAk1otyXVSH0MWMB/ | 9DozwfDb3Ukp7lF1mA8M89pvNhCZtoUzvO2dgWfrJILsc/3NiaAI/DVuxuQs/J65X1iMcJ7a95u4la | 1GZuZ1Qw5UMWeOu8uSKZn3i9zqopZp8p911btB695cusfSuCRvq22pJ5vxrYuiumdA3R7LCaMQ2hAz | +Yoy5pYO+luv4pnogNrq/J7wYmU940IgL55RDypBRtwhVVs+PbU/7tJ//pgPbZkbvVgJEwFhOBDEsf | G3d+TR9OTWp0Ifp+kvLAULsrnTy0BoRIHehWZhl5tcyK2sXMXv/B1CMaMArZQieX69o7RWObwi7dvW | WtYohV71JPes/5mHmYOGXT1WyPgPPK |X-Developer-Key: i=broonie@kernel.org; a=openpgp; | fpr=3F2568AAC26998F9E813A1C5C3F436CA30F5D8EB |X-Spam-Status: No, score=-11.8 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.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-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 |Tested-by: Jeremy Linton |--- | arch/arm64/include/asm/elf.h | 15 ++++++++++++--- | arch/arm64/kernel/process.c | 14 ++------------ | 2 files changed, 14 insertions(+), 15 deletions(-) | |diff --git a/arch/arm64/include/asm/elf.h b/arch/arm64/include/asm/elf.h |index a488a1329b16..43b10fd04467 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 148 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 c8989b999250..2645bc79b35e 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