From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752403AbdLFUrL (ORCPT ); Wed, 6 Dec 2017 15:47:11 -0500 Received: from mail-oi0-f67.google.com ([209.85.218.67]:34433 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751748AbdLFUrK (ORCPT ); Wed, 6 Dec 2017 15:47:10 -0500 X-Google-Smtp-Source: AGs4zMZyb7LhKYNAxjkdy4JPzC4u/s2Js0LTM0U34cunNaIZA2hnAQTvXQzWd5RogdMmt33ePGzypNcXxpGWsJ88feY= MIME-Version: 1.0 In-Reply-To: <20171206171612.v5ucbi6yyeiks2yv@gmail.com> References: <20171206141627.688219-1-arnd@arndb.de> <20171206171612.v5ucbi6yyeiks2yv@gmail.com> From: Arnd Bergmann Date: Wed, 6 Dec 2017 21:47:08 +0100 X-Google-Sender-Auth: b2ihkiP-sRmX6CqDO_JTaRTBq80 Message-ID: Subject: Re: [PATCH] x86/mm/kaiser: avoid 32-bit/PAE build warning To: Ingo Molnar Cc: Dave Hansen , "the arch/x86 maintainers" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 6, 2017 at 6:16 PM, Ingo Molnar wrote: > > * Arnd Bergmann wrote: > >> On Wed, Dec 6, 2017 at 4:08 PM, Dave Hansen wrote: >> > On 12/06/2017 07:03 AM, Arnd Bergmann wrote: >> >> On Wed, Dec 6, 2017 at 3:15 PM, Arnd Bergmann wrote: >> >> >> >> Maybe it's better to just to the last one-line change in include/linux/kaiser.h. >> > >> > Hi Arnd, >> > >> > Are you hitting this in -next? >> > >> > The newest version of this code has a single kpti_init() function that >> > shouldn't have any of these problems. >> >> Yes, this is next-20171206, apparently it came in through tip/auto-latest, >> which still has the same version. > > I'll update the -next version probably later today. Thanks! I just ran into another build error with KAISER: arch/x86/mm/kaiser.c:173:28: error: '__GFP_NOTRACK' undeclared (first use in this function); did you mean '__GFP_NOFAIL'? When you do the update, can you check that it doesn't reference __GFP_NOTRACK? Apparently the flag got removed in 4.15-rc1. Arnd