From: Rob Herring <robh@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: stable@vger.kernel.org, linux-security-module@vger.kernel.org,
devicetree@vger.kernel.org, frowand.list@gmail.com,
robh+dt@kernel.org, sashal@kernel.org, dmitry.kasatkin@gmail.com,
gregkh@linuxfoundation.org, linux-integrity@vger.kernel.org,
zohar@linux.ibm.com
Subject: Re: [PATCH 5.15] of: kexec: Mark ima_{free,stable}_kexec_buffer() as __init
Date: Wed, 6 Sep 2023 15:28:51 -0500 [thread overview]
Message-ID: <169403211998.243709.4772468997015448407.robh@kernel.org> (raw)
In-Reply-To: <20230905-5-15-of-kexec-modpost-warning-v1-1-4138b2e96b4e@kernel.org>
On Tue, 05 Sep 2023 13:36:11 -0700, Nathan Chancellor wrote:
> This commit has no direct upstream equivalent.
>
> After commit d48016d74836 ("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 b69a2afd5afc ("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>
> ---
> drivers/of/kexec.c | 2 +-
> include/linux/of.h | 2 +-
> security/integrity/ima/ima.h | 2 +-
> security/integrity/ima/ima_kexec.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-09-06 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 20:36 [PATCH 5.15] of: kexec: Mark ima_{free,stable}_kexec_buffer() as __init Nathan Chancellor
2023-09-06 20:28 ` Rob Herring [this message]
2023-09-07 11:30 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169403211998.243709.4772468997015448407.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox