Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752320AbeADSR0 (ORCPT + 1 other); Thu, 4 Jan 2018 13:17:26 -0500 Received: from mail-vk0-f67.google.com ([209.85.213.67]:47095 "EHLO mail-vk0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750924AbeADSRZ (ORCPT ); Thu, 4 Jan 2018 13:17:25 -0500 X-Google-Smtp-Source: ACJfBos7+KiEXeiwE6eEExNmNZrDOE/6rwFa/868fD9OPvSYFMvYTg5HHbdUoJHkEPRj2OJZQ1/JOr/1juPNH8J3KgE= MIME-Version: 1.0 From: Kees Cook Date: Thu, 4 Jan 2018 10:17:23 -0800 Message-ID: Subject: PTI build regression with nvidia drivers To: Thomas Gleixner Cc: LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Hi, This was pointed out in a few places, but not forwarded to lkml yet that I saw: https://devtalk.nvidia.com/default/topic/1028222/linux/lts-kernel-patch-for-intel-cpu-vulnerability-breaks-nvidia-driver/post/5230546 Before and after PTI, cpu_tlbstate is a GPL export: $ git show v4.14:arch/x86/mm/init.c | grep cpu_tlbstate DEFINE_PER_CPU_SHARED_ALIGNED(struct tlb_state, cpu_tlbstate) = { EXPORT_SYMBOL_GPL(cpu_tlbstate); But after PTI, inlining or something is dragging cpu_tlbstate into the open, causing build failures. Technically, to avoid regressions for that module, we'll need to drop the GPL marking on that symbol, or find some other solution... -Kees -- Kees Cook Pixel Security