linux-kernel - linux-next: build warning after merge of the iommu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 8 Jun 2021 13:56:41 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Joerg Roedel <joro@...tes.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build warning after merge of the iommu tree

Hi all,

After merging the iommu tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

WARNING: modpost: vmlinux.o(.text.unlikely+0xddf06): Section mismatch in reference from the function detect_ivrs() to the variable .init.data:amd_iommu_force_enable
The function detect_ivrs() references
the variable __initdata amd_iommu_force_enable.
This is often because detect_ivrs lacks a __initdata 
annotation or the annotation of amd_iommu_force_enable is wrong.

Introduced by commit

  b1e650db2cc4 ("iommu/amd: Add amd_iommu=force_enable option")

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped