From: Kees Cook <kees@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Lorenzo Stoakes <ljs@kernel.org>,
Manuel Ebner <manuelebnerli@mailbox.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v1 1/2] kbuild: Mark the kernel image gzip recipes as recursive
Date: Sat, 10 Oct 2026 01:28:50 -0700 [thread overview]
Message-ID: <20261010082817.eddb2f-kees@kernel.org> (raw)
In-Reply-To: <7109f423-7249-49fb-a923-2824711fe197@paulmck-laptop>
On Fri, Oct 09, 2026 at 09:27:57PM -0700, Paul E. McKenney wrote:
> foreground background
> -next Fix -next Fix
>
> make -jN Bug Good Bug Good
>
> kvm.sh [1] Bug Bug Bug Bug
>
> [1] tools/testing/selftests/rcutorture/bin/kvm.sh --build-only --allcpus --configs TREE02 --trust-make
Thanks for the details! IIUC, the difference is the config, not
foreground vs background. kvm-build.sh adds CONFIG_INITRAMFS_SOURCE,
which is compressed with gzip by default. The usr/Makefile target picks
that compressor through a variable, so v1 missed it. Your plain "make
-jN" builds probably had no built-in initramfs, so the kernel image was
the only place where pigz ran, which v1 did cover.
Hopefully v2 has all the missed targets fixed now:
https://lore.kernel.org/lkml/20261010081910.stay.092-kees@kernel.org/T/#m3b466b33f835119bfbd0c1b3c48d2a8a87f31691
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-10-10 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 6:27 [PATCH v1 0/2] kbuild: Give jobserver-exec recipes the jobserver Kees Cook
2026-10-09 6:27 ` [PATCH v1 1/2] kbuild: Mark the kernel image gzip recipes as recursive Kees Cook
2026-10-09 9:08 ` Nicolas Schier
2026-10-09 12:05 ` Lorenzo Stoakes (ARM)
2026-10-09 15:52 ` Paul E. McKenney
2026-10-09 15:51 ` Paul E. McKenney
2026-10-10 2:25 ` Kees Cook
2026-10-10 4:27 ` Paul E. McKenney
2026-10-10 4:46 ` Kees Cook
2026-10-10 5:07 ` Paul E. McKenney
2026-10-10 8:28 ` Kees Cook [this message]
2026-10-10 21:08 ` Paul E. McKenney
2026-10-09 6:27 ` [PATCH v1 2/2] kbuild: Mark the initcall ordering recipe " Kees Cook
2026-10-09 15:20 ` 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=20261010082817.eddb2f-kees@kernel.org \
--to=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=paulmck@kernel.org \
/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.