From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Mimi Zohar <zohar@linux.ibm.com>, linux-integrity@vger.kernel.org
Subject: Re: [PATCH 1/2] ima_kexec.sh: Detect kernel image
Date: Wed, 7 Jan 2026 17:20:00 +0100 [thread overview]
Message-ID: <20260107162000.GD791855@pevik> (raw)
In-Reply-To: <20260107155737.791588-1-pvorel@suse.cz>
Hi all,
...
> + if [ ! -f "$IMA_KEXEC_IMAGE" ]; then
> + uname="$(uname -r)"
> +
> + # x86_64
> + f="/boot/vmlinuz-$uname"
> +
> + # ppc64le, s390x
> + if [ ! -f "$f" ]; then
> + f="/boot/vmlinux-$uname"
> + fi
> +
> + # aarch64
> + if [ ! -f "$f" ]; then
> + f="/boot/Image-$uname"
> + fi
> +
> + # aarch64 often uses compression
> + if [ ! -f "$f" ]; then
> + f="$(ls /boot/Image-$uname.* || true)"
> + fi
> +
> + if [ -f "$f" ]; then
> + IMA_KEXEC_IMAGE="$f"
> + fi
> + fi
> +
> if [ ! -f "$IMA_KEXEC_IMAGE" ]; then
> tst_brk TCONF "kernel image not found, specify path in \$IMA_KEXEC_IMAGE"
> fi
I'm sorry for the noise, I found our s390x emulation actually uses
/boot/image-$uname. I suggest in the end to merge with following diff.
Kind regards,
Petr
+++ testcases/kernel/security/integrity/ima/tests/ima_kexec.sh
@@ -69,18 +69,16 @@ setup()
if [ ! -f "$IMA_KEXEC_IMAGE" ]; then
uname="$(uname -r)"
- # x86_64
- f="/boot/vmlinuz-$uname"
-
- # ppc64le, s390x
- if [ ! -f "$f" ]; then
- f="/boot/vmlinux-$uname"
- fi
-
- # aarch64
- if [ ! -f "$f" ]; then
- f="/boot/Image-$uname"
- fi
+ for f in \
+ /boot/vmlinuz-$uname \
+ /boot/vmlinux-$uname \
+ /boot/Image-$uname \
+ /boot/image-$uname \
+ ; do
+ if [ -f "$f" ]; then
+ break
+ fi
+ done
# aarch64 often uses compression
if [ ! -f "$f" ]; then
prev parent reply other threads:[~2026-01-07 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 15:57 [PATCH 1/2] ima_kexec.sh: Detect kernel image Petr Vorel
2026-01-07 15:57 ` [PATCH 2/2] ima_kexec.sh: Document kernel config dependencies Petr Vorel
2026-01-14 15:11 ` Mimi Zohar
2026-01-14 16:46 ` Petr Vorel
2026-01-07 16:20 ` Petr Vorel [this message]
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=20260107162000.GD791855@pevik \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--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