Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1532211ybg; Tue, 2 Jun 2020 12:33:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzwmC7LVzKNNckymEvd6xGsFEaKaC4WSY6BbNGMcoSTbbymDl7+/iS6kqgQpNVD46E9e5B3 X-Received: by 2002:a17:906:39b:: with SMTP id b27mr10575068eja.421.1591126439173; Tue, 02 Jun 2020 12:33:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591126439; cv=none; d=google.com; s=arc-20160816; b=0S8QuUcbJtcFLUqYoX+X9/nSAV5RqiDaWKJzKqnLT4rgnd7M+lAe64A0HYiZDPzJfE oJl7IHFolomP8pwmD2blYw7c3p+vOEY0B6aWDggF3nN94WrSnZv7IOA/1OtoKXdHOj5/ haRnkdo9CKZo2jdTpEPR9af+icWUO029j01Naanip/nH2upvb+txNd8MQPP+O9/vO0ge ik2VSJJx+MfFno4Uvjmeu/1/KRtsSvoUtIOBbk3qwIqMMSh/yCrRpxpt4uw6Y1ETGjPO 4zzTtJrDELcQd+t5UsTsMISnzY95lV7COMGXUM+IQAFO3pwOJEzFcxe3Gtx4nWpcr25u LeQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:from:subject:references :mime-version:message-id:in-reply-to:date:dkim-signature; bh=rclZP01j1InoS/3XtOg/bC1dGPlx80uQ6aMTFnGzZ2w=; b=Eaf3hJ5HCU77f3a0aZNeAeMq6XdHzXuEa1bkhEQYOUYNoMdN9S/0lFRq71nWDBJsJZ JEv1DxM/tgHICsQ211z9mODi/QSQHHadN+11UwRQ2r2gYFxA7JlAfHyMNlyZZJyQJawd rDBmVpEgWLxCuc/dEiV9yOv981IoPfveDAHfbTgI9YKFzD973m2uSCjuZ9tdKWyXcYwb t06S8dRx6XdQGR+GpE74/zZ1PROUNt3ZUBJJjgllbRfabFXFh8qWQIPXe2jsTXzA3+Zy qwZPgR9YHH9uss+xstreVNKbnTeUjHCXWNJMSBDUMfIDW8RjE+TYrw/B2kIgoDPtT9zh eUVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=lKTcFEgW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b27si844048ejq.568.2020.06.02.12.33.35; Tue, 02 Jun 2020 12:33:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=lKTcFEgW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727946AbgFBTbW (ORCPT + 99 others); Tue, 2 Jun 2020 15:31:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726320AbgFBTbV (ORCPT ); Tue, 2 Jun 2020 15:31:21 -0400 Received: from mail-yb1-xb4a.google.com (mail-yb1-xb4a.google.com [IPv6:2607:f8b0:4864:20::b4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F339C08C5C1 for ; Tue, 2 Jun 2020 12:31:21 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id n7so27146ybh.13 for ; Tue, 02 Jun 2020 12:31:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:in-reply-to:message-id:mime-version:references:subject:from:to :cc; bh=rclZP01j1InoS/3XtOg/bC1dGPlx80uQ6aMTFnGzZ2w=; b=lKTcFEgWzsBAVwkz4pKNgMxfzTA/rGF9JodhNthDiBoH7YkwDBV0kuC35tGrGmUPa7 vigobAbCfGHSoCDBNiiNxGCo7ry+l11xNDbwclXy4FRbvLdz1Yv3eqb8rD4o311vIRV6 NpmILM/4g7+ijufcHgNkg4AdMRRfwaUT1X0pS7DCnceJFn8bDOjsoNsZDYC6xv9nOuWg oBIKuuzUNJbFU0/tAlZtsBNYOjUnDAbe8I0Qxs1y2Ikzs3uN0bccFj+Iby/ZIT//ZKjR fgN+4PcwfA4n6RA2eU1K9QyQilXZEkUcXZqwz2AYKNfI6kQB0S/S7OhaqcgDbolreiHl ZAjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:in-reply-to:message-id:mime-version :references:subject:from:to:cc; bh=rclZP01j1InoS/3XtOg/bC1dGPlx80uQ6aMTFnGzZ2w=; b=L1bc2p9UF0bK0IR7zujmDxMQA+W85K8OmVLCYLH4FYRyHD8ZZx3JJG4UBF6glc4JIl EABWGAZtsjInZEsSgyEj8DuEnw04/W6k9mwtIv2CGpEmZyrzCTfwapn+xG0EEXEcuPBB bh+iWG1HkAgsWw4kjUMroNquo1Gpga3PqE+v4BJF4XZsNY8dXIhLhOrom6DmpFTYqM4P K3SjFlerBBJ4j7j/Eu4sjB9C87rbhd0IseXiIjyyL/9MNeHOYgFs5u5havjItdvozWGt MzjKLunUmJ2V371TLmrJ6uZkANcfZ7crdKRzAYXvt968wglG/sKsHkSH/hrScHnUDbtj 546g== X-Gm-Message-State: AOAM533pxVYeG0lqPtHFvnBEPrE8aTlXcO+FvOVTxBs5fOZmuOOJzhRK bGmA7G7eUbcFst5+QkTkmMmXPVWlp53gscY= X-Received: by 2002:a25:c186:: with SMTP id r128mr46983177ybf.92.1591126280496; Tue, 02 Jun 2020 12:31:20 -0700 (PDT) Date: Tue, 2 Jun 2020 12:30:59 -0700 In-Reply-To: <20200602132702.y3tjwvqdbww7oy5i@treble> Message-Id: <20200602193100.229287-1-inglorion@google.com> Mime-Version: 1.0 References: <20200602132702.y3tjwvqdbww7oy5i@treble> X-Mailer: git-send-email 2.27.0.rc2.251.g90737beb825-goog Subject: [PATCH v2] x86_64: fix jiffies ODR violation From: Bob Haarman To: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Andrew Morton , Josh Poimboeuf Cc: Bob Haarman , stable@vger.kernel.org, Nathan Chancellor , Alistair Delva , Fangrui Song , Nick Desaulniers , Sami Tolvanen , Andi Kleen , x86@kernel.org, "H. Peter Anvin" , afzal mohammed , Kyung Min Park , Peter Zijlstra , Kees Cook , Heiko Carstens , Baoquan He , Thomas Lendacky , "H.J. Lu" , Ross Zwisler , Arvind Sankar , Dmitry Safonov <0x7f454c46@gmail.com>, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 'jiffies' and 'jiffies_64' are meant to alias (two different symbols that share the same address). Most architectures make the symbols alias to the same address via linker script assignment in their arch//kernel/vmlinux.lds.S: jiffies = jiffies_64; which is effectively a definition of jiffies. jiffies and jiffies_64 are both forward declared for all arch's in: include/linux/jiffies.h. jiffies_64 is defined in kernel/time/timer.c for all arch's. x86_64 was peculiar in that it wasn't doing the above linker script assignment, but rather was: 1. defining jiffies in arch/x86/kernel/time.c instead via linker script. 2. overriding the symbol jiffies_64 from kernel/time/timer.c in arch/x86/kernel/vmlinux.lds.s via 'jiffies_64 = jiffies;'. As Fangrui notes: In LLD, symbol assignments in linker scripts override definitions in object files. GNU ld appears to have the same behavior. It would probably make sense for LLD to error "duplicate symbol" but GNU ld is unlikely to adopt for compatibility reasons. So we have an ODR violation (UB), which we seem to have gotten away with thus far. Where it becomes harmful is when we: 1. Use -fno-semantic-interposition. As Fangrui notes: Clang after LLVM commit 5b22bcc2b70d ("[X86][ELF] Prefer to lower MC_GlobalAddress operands to .Lfoo$local") defaults to -fno-semantic-interposition similar semantics which help -fpic/-fPIC code avoid GOT/PLT when the referenced symbol is defined within the same translation unit. Unlike GCC -fno-semantic-interposition, Clang emits such relocations referencing local symbols for non-pic code as well. This causes references to jiffies to refer to '.Ljiffies$local' when jiffies is defined in the same translation unit. Likewise, references to jiffies_64 become references to '.Ljiffies_64$local' in translation units that define jiffies_64. Because these differ from the names used in the linker script, they will not be rewritten to alias one another. Combined with ... 2. Full LTO effectively treats all source files as one translation unit, causing these local references to be produced everywhere. When the linker processes the linker script, there are no longer any references to jiffies_64' anywhere to replace with 'jiffies'. And thus '.Ljiffies$local' and '.Ljiffies_64$local' no longer alias at all. In the process of porting patches enabling Full LTO from arm64 to x86_64, we observe spooky bugs where the kernel appeared to boot, but init doesn't get scheduled. Instead, we can avoid the ODR violation by matching other arch's by defining jiffies only by linker script. For -fno-semantic-interposition + Full LTO, there is no longer a global definition of jiffies for the compiler to produce a local symbol which the linker script won't ensure aliases to jiffies_64. Link: https://github.com/ClangBuiltLinux/linux/issues/852 Fixes: 40747ffa5aa8 ("asmlinkage: Make jiffies visible") Cc: stable@vger.kernel.org Reported-by: Nathan Chancellor Reported-by: Alistair Delva Suggested-by: Fangrui Song Debugged-by: Nick Desaulniers Debugged-by: Sami Tolvanen Signed-off-by: Bob Haarman Reviewed-by: Andi Kleen Reviewed-by: Josh Poimboeuf --- v2: * Changed commit message as requested by Josh Poimboeuf (no code change) --- arch/x86/kernel/time.c | 4 ---- arch/x86/kernel/vmlinux.lds.S | 4 ++-- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/arch/x86/kernel/time.c b/arch/x86/kernel/time.c index 371a6b348e44..e42faa792c07 100644 --- a/arch/x86/kernel/time.c +++ b/arch/x86/kernel/time.c @@ -25,10 +25,6 @@ #include #include -#ifdef CONFIG_X86_64 -__visible volatile unsigned long jiffies __cacheline_aligned_in_smp = INITIAL_JIFFIES; -#endif - unsigned long profile_pc(struct pt_regs *regs) { unsigned long pc = instruction_pointer(regs); diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S index 1bf7e312361f..7c35556c7827 100644 --- a/arch/x86/kernel/vmlinux.lds.S +++ b/arch/x86/kernel/vmlinux.lds.S @@ -40,13 +40,13 @@ OUTPUT_FORMAT(CONFIG_OUTPUT_FORMAT) #ifdef CONFIG_X86_32 OUTPUT_ARCH(i386) ENTRY(phys_startup_32) -jiffies = jiffies_64; #else OUTPUT_ARCH(i386:x86-64) ENTRY(phys_startup_64) -jiffies_64 = jiffies; #endif +jiffies = jiffies_64; + #if defined(CONFIG_X86_64) /* * On 64-bit, align RODATA to 2MB so we retain large page mappings for -- 2.27.0.rc2.251.g90737beb825-goog