From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932905AbeEHQZF (ORCPT ); Tue, 8 May 2018 12:25:05 -0400 Received: from mga18.intel.com ([134.134.136.126]:14953 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932707AbeEHQZE (ORCPT ); Tue, 8 May 2018 12:25:04 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,379,1520924400"; d="scan'208";a="39652780" Subject: Re: [PATCH] x86/boot/64/clang: Use fixup_pointer() to access '__supported_pte_mask' To: Alexander Potapenko References: <20180508121638.174022-1-glider@google.com> <1f69bdb6-df5e-d709-064a-4f6fdd6e11a7@linux.intel.com> Cc: Ingo Molnar , "Kirill A. Shutemov" , Linux Memory Management List , LKML , Matthias Kaehlcke , Dmitriy Vyukov , Michael Davidson From: Dave Hansen Openpgp: preference=signencrypt Message-ID: Date: Tue, 8 May 2018 09:25:01 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/08/2018 07:50 AM, Alexander Potapenko wrote: >>> Similarly to commit 187e91fe5e91 >>> ("x86/boot/64/clang: Use fixup_pointer() to access 'next_early_pgt'"), >>> '__supported_pte_mask' must be also accessed using fixup_pointer() to >>> avoid position-dependent relocations. >>> >>> Signed-off-by: Alexander Potapenko >>> Fixes: fb43d6cb91ef ("x86/mm: Do not auto-massage page protections") > >> In the interests of standalone changelogs, I'd really appreciate an >> actual explanation of what's going on here. Your patch makes the code >> uglier and doesn't fix anything functional from what I can see. > You're right, sure. I'll send a patch with an updated description. Great, thanks! >> Do we have anything we can do to keep us from recreating these kinds of >> regressions all the time? > I'm not really aware of the possible options in the kernel land. Looks like > a task for some objtool-like utility? > As long as these regressions are caught with Clang, setting up a 0day Clang > builder might help. I've asked the 0day folks if this is doable. It would be great to see it added.