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 X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0FC29C433E1 for ; Wed, 15 Jul 2020 00:41:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E3D4A20674 for ; Wed, 15 Jul 2020 00:41:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727981AbgGOAlh (ORCPT ); Tue, 14 Jul 2020 20:41:37 -0400 Received: from mail-qv1-f65.google.com ([209.85.219.65]:41572 "EHLO mail-qv1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726970AbgGOAlh (ORCPT ); Tue, 14 Jul 2020 20:41:37 -0400 Received: by mail-qv1-f65.google.com with SMTP id t7so157998qvl.8 for ; Tue, 14 Jul 2020 17:41:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=+QF4vAUUBnYQYLQ3yHUBiViRPlxMNrC6DIkF6ybdH8Q=; b=lI2fHMJkyZ88ogHTpZerGIFbF70izqwUGybOsUXKvWMvLZRZve9+9lBAhaqPLog6rI ZMTIRcrucj2lT8Wqz8QyDhYlddPKH8767gql+/7oWHoTqfgFmhtY/DLrlTODGW4ra0fO zEjhK/5xlDPD2O0hj0xie2J96h2F2K0RPZqTEaq6PRhyw94liiMfrRuqP7mpUjw/H1tq m/smpTzPZ0p5nn31H868BcGiIgL/YrftUih9EeolomrnWUhCTrylNzB+c0u8yyvtwbMl LWYTef5cETAfKN8TWrWjQjH+v1zdXUaaMwmccEKsf98aBawcfZCVmvNRmKxOWtc1U1qT GqQQ== X-Gm-Message-State: AOAM5310up/5Tg6pFvaPKbuS/7kO6XwqlaKUawnqjkBMHqBEwH3ewufw fRJ6spAQJxuXiL+QfBfVX/k= X-Google-Smtp-Source: ABdhPJz9p65GCuuiFsrJjp3DnxX4zcqi8/y5XU6Z8si/eCnnBu1hub2R6ThEFHUJkmWiP7BrKCeucw== X-Received: by 2002:a0c:f307:: with SMTP id j7mr7147998qvl.55.1594773695221; Tue, 14 Jul 2020 17:41:35 -0700 (PDT) Received: from rani.riverdale.lan ([2001:470:1f07:5f3::b55f]) by smtp.gmail.com with ESMTPSA id c9sm524776qko.24.2020.07.14.17.41.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Jul 2020 17:41:34 -0700 (PDT) From: Arvind Sankar To: Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org Cc: Nick Desaulniers , Fangrui Song , Dmitry Golovin , clang-built-linux@googlegroups.com, Ard Biesheuvel , Masahiro Yamada , Daniel Kiper , Sedat Dilek , Kees Cook , Nathan Chancellor , Arnd Bergmann , "H . J . Lu" , linux-kernel@vger.kernel.org Subject: [PATCH v5 0/7] x86/boot: Remove run-time relocations from compressed kernel Date: Tue, 14 Jul 2020 20:41:26 -0400 Message-Id: <20200715004133.1430068-1-nivedita@alum.mit.edu> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200714023836.2310569-1-nivedita@alum.mit.edu> References: <20200714023836.2310569-1-nivedita@alum.mit.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The compressed kernel currently contains bogus run-time relocations in the startup code in head_{32,64}.S, which are generated by the linker, but must not actually be processed at run-time. This generates warnings when linking with the BFD linker, and errors with LLD, which defaults to erroring on run-time relocations in read-only sections. It also requires the -z noreloc-overflow hack for the 64-bit kernel, which prevents us from linking it as -pie on an older BFD linker (<= 2.26) or on LLD, because the locations that are to be apparently relocated are only 32-bits in size and so cannot really have R_X86_64_RELATIVE relocations. This series aims to get rid of these relocations. I've build- and boot-tested with combinations of clang/gcc-10 with lld/bfd-2.34, and gcc-4.9.0 with bfd-2.24, skipping clang on 32-bit because it currently has other issues [0]. The first three patches by Ard remove indirection via the GOT from the compressed kernel code. The next patch is an independent fix for LLD, to avoid an orphan section in arch/x86/boot/setup.elf. The fifth patch gets rid of almost all the relocations. It uses standard PIC addressing technique for 32-bit, i.e. loading a register with the address of _GLOBAL_OFFSET_TABLE_ and then using GOTOFF references to access variables. For 64-bit, there is 32-bit code that cannot use RIP-relative addressing, and also cannot use the 32-bit method, since GOTOFF references are 64-bit only. This is instead handled using a macro to replace a reference like gdt with (gdt-startup_32) instead. The assembler will generate a PC32 relocation entry, with addend set to (.-startup_32), and these will be replaced with constants at link time. This works as long as all the code using such references lives in the same section as startup_32, i.e. in .head.text. The sixth patch addresses a remaining issue with the BFD linker, which generates run-time relocations for absolute symbols. We use z_input_len and z_output_len, defined in the generated piggy.S file, as symbols whose absolute "addresses" are actually the size of the compressed payload and the size of the decompressed kernel image respectively. LLD does not generate relocations for these two symbols, but the BFD linker does, prior to the upcoming 2.35. To get around this, piggy.S is extended to also define two u32 variables (in .rodata) with the lengths, and the head code is modified to use those instead of the symbol addresses. An alternative way to handle z_input_len/z_output_len would be to just include piggy.S in head_{32,64}.S instead of as a separate object file, since the GNU assembler doesn't generate relocations for symbols set to constants. The last patch adds a check in the linker script to ensure that no run-time relocations get reintroduced. [0] https://lore.kernel.org/lkml/20200504230309.237398-1-ndesaulniers@google.com/ Changes from v4: - Move -pie --no-dynamic-linker from KBUILD_LDFLAGS to LDFLAGS_vmlinux Sedat: I'm not clear on whether you tested with the final LDFLAGS, could you confirm: i.e. if you tested with -pie passed to LLD? - Replace runtime -> run-time to be consistent in wording Changes from v3: - Move hidden.h to include/linux so the EFI stub and the compressed kernel can share the same file Changes from v2: - Incorporate Ard's patches for eliminating GOT references into this series - Rebase on v5.8-rc3 v2: https://lore.kernel.org/lkml/20200525225918.1624470-1-nivedita@alum.mit.edu/ Changes from v1: - Add .text.* to setup.ld instead of just .text.startup - Rename the la() macro introduced in the second patch for 64-bit to rva(), and rework the explanatory comment. - In the last patch, check both .rel.dyn and .rela.dyn, instead of just one per arch. Ard Biesheuvel (3): x86/boot/compressed: Move .got.plt entries out of the .got section x86/boot/compressed: Force hidden visibility for all symbol references x86/boot/compressed: Get rid of GOT fixup code Arvind Sankar (4): x86/boot: Add .text.* to setup.ld x86/boot: Remove run-time relocations from .head.text code x86/boot: Remove run-time relocations from head_{32,64}.S x86/boot: Check that there are no run-time relocations arch/x86/boot/compressed/Makefile | 39 +----- arch/x86/boot/compressed/head_32.S | 99 +++++---------- arch/x86/boot/compressed/head_64.S | 165 ++++++++++--------------- arch/x86/boot/compressed/mkpiggy.c | 6 + arch/x86/boot/compressed/vmlinux.lds.S | 24 +++- arch/x86/boot/setup.ld | 2 +- drivers/firmware/efi/libstub/Makefile | 2 +- drivers/firmware/efi/libstub/hidden.h | 6 - include/linux/hidden.h | 19 +++ 9 files changed, 153 insertions(+), 209 deletions(-) delete mode 100644 drivers/firmware/efi/libstub/hidden.h create mode 100644 include/linux/hidden.h base-commit: e9919e11e219eaa5e8041b7b1a196839143e9125 -- 2.26.2