From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B00DDC4167B for ; Mon, 4 Dec 2023 07:03:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234579AbjLDHDE (ORCPT ); Mon, 4 Dec 2023 02:03:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234535AbjLDHDC (ORCPT ); Mon, 4 Dec 2023 02:03:02 -0500 Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9F12CB3; Sun, 3 Dec 2023 23:03:08 -0800 (PST) Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-50bf69afa99so774968e87.3; Sun, 03 Dec 2023 23:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701673387; x=1702278187; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=mFUgMaJywl8iY3lwSLQMnwve6+5rhLeubZxAaYe0ZgQ=; b=Mr1x1T236cj1C4MR/Ox1IUBgUuR+bcvT5E2Uj3AzvMP44oOxXttGq+7mBGVNitYYML hf+IfUGlolr8aB3ImXoOHSR8jU2FsJmM7m1fD31NUlkOhIEgCM0HYmm9ToosIqypF6qY dmfLHV4/WBoVUMZt2ao6yvGynRXZQSDjhpEOvELMt2y9T1M4UVLmFD8C1ABsqsv63imc NDJIKj604QwidHB/fe+yMDjXlBcSlg9tYr25slqUygXmeSiGOvZiWWw7j/gUE7UstiiW ietFuXNIApQL/HdPwhCswuoY/J2R94I8B+/dlG9icAw0jczxXsGZAZp8jDOETOoMWUMS rUnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701673387; x=1702278187; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mFUgMaJywl8iY3lwSLQMnwve6+5rhLeubZxAaYe0ZgQ=; b=k1NUJfvYgvmrGcFEr3EnkHm0gqtZQfDPS6RWk41SYpjYEIMiy6D7YFF4zVmsUCa906 3O5GrQW2ksVpTOzKfDY+CyRc7tdTkUw7kPh82KCfhPdl/dlH+aTXOQBjhrB6a+zOOKUc jqpnkHOG8lYlVScUA2hQW8/K15PyMniJa2EFFkB93UDLCqJbpTtz33cO8qhXnFir1P2/ ua0/mOd4sgL3RQwEWINc/Dni+ZRdIRtbgQkZ3VYjBk0g5ZVlZcBsLFLJ4gLt926qtb8f WqBeWArSkQKwz7im8RPXIkqzHCSJ7ngwmfzsmF/ii9pImSio86lhFKq96casIyna6ZK+ 3i/w== X-Gm-Message-State: AOJu0YyHYpH+rrZ4K6jv3EhaF7gSimQq/6Aewt1d3XfM3pDLZrLx5lv9 A4jb9hBWFSJL/s/LPVf0e5phBHWXaGoSsi4JVKs= X-Google-Smtp-Source: AGHT+IG4mSgeMfIz8vSVWdJ7/GRsWTH49RJsDEc7HjPDv3AQgSOA4PAfj1zvgmdjtB/v06TFUPvMCvSNub6v4d9vOzc= X-Received: by 2002:a05:6512:baa:b0:509:8a5e:654d with SMTP id b42-20020a0565120baa00b005098a5e654dmr3481368lfv.21.1701673386539; Sun, 03 Dec 2023 23:03:06 -0800 (PST) MIME-Version: 1.0 References: <20231201112918.294b40b1@canb.auug.org.au> <20231204150807.600c2f09@canb.auug.org.au> In-Reply-To: <20231204150807.600c2f09@canb.auug.org.au> From: Uros Bizjak Date: Mon, 4 Dec 2023 08:02:56 +0100 Message-ID: Subject: Re: linux-next: build warnings after merge of the tip tree To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Ingo Molnar , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 4, 2023 at 5:08=E2=80=AFAM Stephen Rothwell wrote: > > Hi Uros, > > On Fri, 1 Dec 2023 13:09:45 +0100 Uros Bizjak wrote: > > > > On Fri, Dec 1, 2023 at 1:29=E2=80=AFAM Stephen Rothwell wrote: > > > > > After merging the tip tree, today's linux-next build (x86_64 allmodcon= fig) > > > produced these warnings: > > > > > > WARNING: modpost: EXPORT symbol "const_pcpu_hot" [vmlinux] version ge= neration failed, symbol will not be versioned. > > > Is "const_pcpu_hot" prototyped in ? > > > WARNING: modpost: "const_pcpu_hot" [arch/x86/kernel/msr.ko] has no CR= C! > > > WARNING: modpost: "const_pcpu_hot" [arch/x86/kvm/kvm.ko] has no CRC! > > > > My build doesn't produce any warnings. A defconfig + enabling kvm.ko as= module: > > > > ... > > AR built-in.a > > AR vmlinux.a > > LD vmlinux.o > > OBJCOPY modules.builtin.modinfo > > GEN modules.builtin > > MODPOST Module.symvers > > CC .vmlinux.export.o > > CC [M] arch/x86/kvm/kvm.mod.o > > CC [M] fs/efivarfs/efivarfs.mod.o > > ... > > > > Does the attached patch help? Or is there anything else I should do to > > trigger the above problem? > > The patch does not help. I am just doing an X86_64 allmodconfig build > with CONFIG_WERROR=3Dn. gcc is > > $ x86_64-linux-gnu-gcc --version > x86_64-linux-gnu-gcc (Debian 13.2.0-2) 13.2.0 > > This is a cross build with a ppc64le host. The warning is triggered by CONFIG_MODVERSIONS=3Dy and will be fixed in a different way by the patch in [1]. [1] https://lore.kernel.org/lkml/20231203232017.994963-1-ubizjak@gmail.com/ Thanks, Uros.