linux

iv/linux

Files

Nathan Chancellor 7039aa1be9 of: kexec: Mark ima_{free,stable}_kexec_buffer() as __init

This commit has no direct upstream equivalent.

After commit d48016d748 ("mm,ima,kexec,of: use memblock_free_late from
ima_free_kexec_buffer") in 5.15, there is a modpost warning for certain
configurations:

  WARNING: modpost: vmlinux.o(.text+0xb14064): Section mismatch in reference from the function ima_free_kexec_buffer() to the function .init.text:__memblock_free_late()
  The function ima_free_kexec_buffer() references
  the function __init __memblock_free_late().
  This is often because ima_free_kexec_buffer lacks a __init
  annotation or the annotation of __memblock_free_late is wrong.

In mainline, there is no issue because ima_free_kexec_buffer() is marked
as __init, which was done as part of commit b69a2afd5a ("x86/kexec:
Carry forward IMA measurement log on kexec") in 6.0, which is not
suitable for stable.

Mark ima_free_kexec_buffer() and its single caller
ima_load_kexec_buffer() as __init in 5.15, as ima_load_kexec_buffer() is
only called from ima_init(), which is __init, clearing up the warning.

Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

2023-09-19 12:22:30 +02:00

apparmor

apparmor: fix missing error check for rhashtable_insert_fast

2023-07-23 13:47:30 +02:00

bpf

bpf: Implement task local storage

2020-11-06 08:08:37 -08:00

integrity

of: kexec: Mark ima_{free,stable}_kexec_buffer() as __init

2023-09-19 12:22:30 +02:00

keys

security: keys: perform capable check only on privileged operations