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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 03 Jan 2021 16:43:55 +0000
From:   Marc Zyngier <>
To:     Arnd Bergmann <>
Cc:     Catalin Marinas <>,
        Will Deacon <>, Arnd Bergmann <>,
        James Morse <>,
        Julien Thierry <>,
        Suzuki K Poulose <>,
        David Brazdil <>,
        Paolo Bonzini <>,
        Sean Christopherson <>,
        Andrew Scull <>,,,
Subject: Re: [PATCH] KVM: arm64: remove incorrect __init annotation

On Sun, 03 Jan 2021 14:00:50 +0000,
Arnd Bergmann <> wrote:
> From: Arnd Bergmann <>
> When hyp_cpu_pm_exit() is not inlined, it causes a link time warning:
> WARNING: modpost: vmlinux.o(.text+0x39974): Section mismatch in reference from the function kvm_arch_init() to the function .init.text:hyp_cpu_pm_exit()
> The function kvm_arch_init() references
> the function __init hyp_cpu_pm_exit().
> This is often because kvm_arch_init lacks a __init
> annotation or the annotation of hyp_cpu_pm_exit is wrong.
> This is not only called at boot time, so remove the annotation
> to prevent undefined behavior in case it gets called after being
> freed.

It *is* only called at boot time (despite these functions being called
from module_init(), KVM cannot be built as a module on arm64).

The annotations are wrong nonetheless.

> Signed-off-by: Arnd Bergmann <>

Posted here [1], and queued for the next batch of fixes.



Without deviation from the norm, progress is not possible.

Powered by blists - more mailing lists