From: sashiko-bot@kernel.org
To: "Shuah Khan" <skhan@linuxfoundation.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Alexander Graf" <graf@amazon.com>,
"Nicolas Schier" <nsc@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Maximilian Huber" <maximilian.huber@tngtech.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Willy Tarreau" <w@1wt.eu>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Luis Augenstein" <luis.augenstein@tngtech.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, "Askar Safin" <safinaskar@gmail.com>,
linux-kbuild@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH v3 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/
Date: Fri, 25 Sep 2026 19:38:07 +0000 [thread overview]
Message-ID: <20260925193807.70F401F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260925-move-gen_init_cpio-to-scripts-v3-2-99c493f76722@kernel.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] selftests/liveupdate: vmtest.sh mkinitrd fails due to missing gen_init_cpio
- [Low] kbuild: stale comment in gen_initramfs.sh assumes old usr/ location
--
commit 97c7fb8e47f1b247f157846cfecd29ff5f239ed1
Author: Nicolas Schier <nsc@kernel.org>
kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/
gen_init_cpio and gen_initramfs.sh are part of kbuild and required for
all kernel builds w/ CONFIG_BLK_DEV_INITRD. Move both to scripts/ to be
more clear about their importance.
Link: https://lore.kernel.org/all/aSdrCFkUQup3qb-q@derry.ads.avm.de/
> diff --git a/tools/testing/selftests/kho/vmtest.sh b/tools/testing/selftests/kho/vmtest.sh
> index 0014bd76e88de..1e86ffcc3a79e 100755
> --- a/tools/testing/selftests/kho/vmtest.sh
> +++ b/tools/testing/selftests/kho/vmtest.sh
> @@ -100,7 +100,7 @@ file /init $tmp_dir/init 0755 0 0
> file /kernel $kernel 0644 0 0
> EOF
>
> - "$build_dir/usr/gen_init_cpio" "$tmp_dir/cpio_list" > "$initrd"
> + "$build_dir/scripts/gen_init_cpio" "$tmp_dir/cpio_list" > "$initrd"
> }
[Severity: Medium]
The path for the kho selftest was updated, but it looks like
tools/testing/selftests/liveupdate/vmtest.sh also still calls the old path.
For example, in its mkinitrd():
# Generate inner_initrd.cpio
"$build_dir/usr/gen_init_cpio" "$workspace_dir/cpio_list_inner" > "$workspace_dir/inner_initrd.cpio"
and again later in the same function:
# Generate the final initrd
"$build_dir/usr/gen_init_cpio" "$workspace_dir/cpio_list" > "$initrd"
Since this patch ensures the old artifact is removed via
scripts/remove-stale-files, will the liveupdate selftest unconditionally
fail because it cannot find gen_init_cpio?
Should liveupdate/vmtest.sh be updated to use scripts/gen_init_cpio as well?
> diff --git a/usr/gen_initramfs.sh b/scripts/gen_initramfs.sh
> similarity index 99%
> rename from usr/gen_initramfs.sh
> rename to scripts/gen_initramfs.sh
> index 7eba2fddf0ef2..27ac1fd48001a 100755
> --- a/usr/gen_initramfs.sh
> +++ b/scripts/gen_initramfs.sh
> @@ -247,4 +247,4 @@ done
>
> # If output_file is set we will generate cpio archive
> # we are careful to delete tmp files
> -usr/gen_init_cpio $output $timestamp $cpio_list
> +scripts/gen_init_cpio $output $timestamp $cpio_list
[Severity: Low]
Is the script header comment now out of date?
At the top of the renamed scripts/gen_initramfs.sh it still states:
# Generate a cpio packed initramfs. It uses gen_init_cpio to generate
# the cpio archive.
# This script assumes that gen_init_cpio is located in usr/ directory
Should this comment be updated to reflect the new scripts/ location?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260925-move-gen_init_cpio-to-scripts-v3-1-99c493f76722@kernel.org?part=2
next prev parent reply other threads:[~2026-09-25 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 19:29 [PATCH v3 0/2] Move tool for generating initramfs cpio to scripts/ Nicolas Schier
2026-09-25 19:29 ` [PATCH v3 1/2] kbuild: Mark usr_gen_init_cpio as no-dot-config-target Nicolas Schier
2026-09-25 19:33 ` sashiko-bot
2026-09-25 19:29 ` [PATCH v3 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/ Nicolas Schier
2026-09-25 19:38 ` sashiko-bot [this message]
2026-09-26 8:34 ` [PATCH v3 0/2] Move tool for generating initramfs cpio " Mike Rapoport
2026-09-26 17:48 ` Nicolas Schier
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=20260925193807.70F401F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=corbet@lwn.net \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=luis.augenstein@tngtech.com \
--cc=maximilian.huber@tngtech.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=safinaskar@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.