Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp726050ima; Fri, 1 Feb 2019 10:01:39 -0800 (PST) X-Google-Smtp-Source: AHgI3IauilJVXeJF71L07c163t2dDKNjp2MU+3YsbOKhGlELKui9CV9X8tH9t3FGx03pxo3cTSgz X-Received: by 2002:a65:49c9:: with SMTP id t9mr3081074pgs.184.1549044099417; Fri, 01 Feb 2019 10:01:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549044099; cv=none; d=google.com; s=arc-20160816; b=RyMOv3ApEeE26GpskbGZO6/shxtDvPY48k5EYU+mSBhI9zIHasoEstrOsD1Lm6co9c icZdlDHHbgJl+h+IYM/GgA5aHmU1HeWEtWUgV1KojfE8d7otE/lhoTnC+VjkKNNmb/he IBx3S/iJMy+3x0eOSYHov04jr/IU9Rif4loPpm++m+07cESJkkJZbD/Sz1D80yVWBxgF qHmuolMOYPeyVcAiYINxeIyCmJdJ2I+h0xVKts9RL2F2RxAXeTPzY5RmWdiuf48MXNCN XZuMYH61gjV8OZSPvgOhFnOor9vN4irPrJLhrGXmNDMG5XQeEih2kfYT/Rib+Bbe09Ww HLLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=3IsB4n7mKE/XOdrocSJSPhNR5SNx/kKR4kJ8kiC66QM=; b=GimMtlkcr701ExdtcCT+zVI4fY/CMTlofB4seTeKBcml2UCdPJKjZ7Unp2NetvHi46 IoWQ5TcSL2ikssskG+jN29HzqaaHhEdC7JdY5jxk3MaitrOnOxHEka/smJAR7tKL93Ve 7Upps652L4/8VqOkZhU1wGDwY09kY/w9HQzksCytyblmkXhJw1vBoTdveWp/vpZOHp40 052p5owmQT+MhHROmCHMZNbJS3YPjmbHIZGrFZxq8SR7sfD1uGv5Pyb0FSuK45ruzzxL Bkdu8GVGM9jbIiICBDPyx1/FvfG4/UPpGYcGdq5Xq5HF0SO9RzKBjXbMPKXMpGrGL3ne +Pig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=HhykiPcp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o3si8001037pll.201.2019.02.01.10.01.23; Fri, 01 Feb 2019 10:01:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=HhykiPcp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731206AbfBARON (ORCPT + 99 others); Fri, 1 Feb 2019 12:14:13 -0500 Received: from mail-io1-f65.google.com ([209.85.166.65]:39283 "EHLO mail-io1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726542AbfBARON (ORCPT ); Fri, 1 Feb 2019 12:14:13 -0500 Received: by mail-io1-f65.google.com with SMTP id k7so6273316iob.6 for ; Fri, 01 Feb 2019 09:14:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3IsB4n7mKE/XOdrocSJSPhNR5SNx/kKR4kJ8kiC66QM=; b=HhykiPcpS6Uqq0FPjVQ8T6y9OaqrOk2SijfsLB1PkRWQC7PWcIUOWl/aaf8lilYOo0 OE75O5newfSH3Sm+iQi+ucMWdCikq/+lF/HMd8U0UK7XWRCjikQhxUDdw7hsr3cyAb2E X6Gb9doVNEi6VdmKUNXx9HHD25il1wQne4fcU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3IsB4n7mKE/XOdrocSJSPhNR5SNx/kKR4kJ8kiC66QM=; b=Zjc8L5iKPEJ+sc2Rz5IbA687huKOfWNwc4eLsc3cZK3lC1mr3u5ytZ8tVtak9GjNrK SSa6tGkVdo1DTcRZCo4ve/49VuB9o9i6XIMTVumIAp7JetO6Q6/xpx94Werc2AYBM9aR TiAakSSqvCKLKTrRk1HsVBzYly2nj8zUVMy9DL0xycBG+UaVWdjH0ewqLBa5CoMKBI3X HVgoO+RdNCcnASy176wNs6/Avd0ujWjzi8/VFqYc0iQNtMp/MfFm04HKuV2CoAYb1MGw KujvcJQtLep9KeBwp3rGaloX2hJd9lIeBQpKWJA6YHZ1uzwY04AOOkNNJNSwU3BemMiw uiHA== X-Gm-Message-State: AHQUAuYuNgm4c7TphmsKe78YbwwrT/0E18s0+0RAn6+OWRSq/PFc7EfP jfKPVQgBIrdkMCk/QXS9quQdQK/f2PA= X-Received: by 2002:a5d:85c5:: with SMTP id e5mr21939546ios.125.1549041252108; Fri, 01 Feb 2019 09:14:12 -0800 (PST) Received: from mail-it1-f173.google.com (mail-it1-f173.google.com. [209.85.166.173]) by smtp.gmail.com with ESMTPSA id e68sm1493685ite.7.2019.02.01.09.14.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 09:14:11 -0800 (PST) Received: by mail-it1-f173.google.com with SMTP id z20so10824246itc.3 for ; Fri, 01 Feb 2019 09:14:10 -0800 (PST) X-Received: by 2002:a24:d081:: with SMTP id m123mr2034035itg.119.1549041249599; Fri, 01 Feb 2019 09:14:09 -0800 (PST) MIME-Version: 1.0 References: <20190131192533.34130-1-thgarnie@chromium.org> <20190131192533.34130-15-thgarnie@chromium.org> <01000168a5b35a86-b79bfe67-191e-43bc-a5c7-0e74eac06195-000000@email.amazonses.com> <01000168a6e5ab88-0deea73f-387f-4941-bd11-d1c161aac88a-000000@email.amazonses.com> In-Reply-To: <01000168a6e5ab88-0deea73f-387f-4941-bd11-d1c161aac88a-000000@email.amazonses.com> From: Thomas Garnier Date: Fri, 1 Feb 2019 09:13:58 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v6 14/27] x86/percpu: Adapt percpu for PIE support To: Christopher Lameter Cc: Kernel Hardening , kristen@linux.intel.com, Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , "the arch/x86 maintainers" , Dennis Zhou , Tejun Heo , Boris Ostrovsky , Juergen Gross , Stefano Stabellini , Andrew Morton , Andi Kleen , "Kirill A. Shutemov" , Michal Hocko , Mike Rapoport , Stephen Rothwell , Cao jin , Brijesh Singh , Masahiro Yamada , Joerg Roedel , Peter Zijlstra , Kees Cook , Mathieu Desnoyers , LKML , xen-devel 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 On Thu, Jan 31, 2019 at 6:31 PM Christopher Lameter wrote: > > On Thu, 31 Jan 2019, Thomas Garnier wrote: > > > The per-cpu symbols are in a section that is zero based to create > > offsets. The compiler doesn't see them as offsets but as relative > > symbol and try to relocate them. Given the distance between zero and > > the mapped kernel is much larger than the instruction offset range, it > > fails to do it. > > We switch that off in the linker. If that does not work with your > modifications then you need to figure out how to update the link > configuration. > It didn't work originally but I will revisit to see if I missed something.