From: Joe Lawrence <joe.lawrence@redhat.com>
To: Jan Stancek <jstancek@redhat.com>,
maddy@linux.ibm.com, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com, christophe.leroy@csgroup.eu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/tools: drop `-o pipefail` in gcc check scripts
Date: Thu, 28 Aug 2025 09:32:18 -0400 [thread overview]
Message-ID: <0ab92ae3-674f-445e-883c-0e511add85d2@redhat.com> (raw)
In-Reply-To: <e8c743dfb16c6c00fd793d7afa6eed33c49f895f.1756202009.git.jstancek@redhat.com>
On 8/26/25 5:54 AM, Jan Stancek wrote:
> We've been observing rare non-deterministic kconfig failures during
> olddefconfig, where ARCH_USING_PATCHABLE_FUNCTION_ENTRY was getting
> disabled and with it number of other config options that depend on it.
>
> The reason is that gcc-check-fpatchable-function-entry.sh can fail
> if `grep -q` (or scripts/dummy-tools/gcc) is fast enough to exit while
> there is still someone writing on other side of pipe. `pipefail`
> propagates that error up to kconfig.
>
> This can be seen for example with:
> # (set -e; set -o pipefail; yes | grep -q y); echo $?
> 141
>
> or by running the actual check script in loop extensively:
> ----------------------------- 8< -------------------------------
> function kconfig()
> {
> for i in `seq 1 100`; do
> arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh \
> ./scripts/dummy-tools/gcc -mlittle-endian \
> || { echo "Oops"; exit 1; }
> done
> }
>
> for ((i=0; i<$(nproc); i++)); do kconfig & done
> wait; echo "Done"
> ----------------------------- >8 -------------------------------
>
> Fixes: 0f71dcfb4aef ("powerpc/ftrace: Add support for -fpatchable-function-entry")
> Fixes: b71c9ffb1405 ("powerpc: Add arch/powerpc/tools directory")
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> ---
> arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh | 1 -
> arch/powerpc/tools/gcc-check-mprofile-kernel.sh | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh b/arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh
> index 06706903503b..baed467a016b 100755
> --- a/arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh
> +++ b/arch/powerpc/tools/gcc-check-fpatchable-function-entry.sh
> @@ -2,7 +2,6 @@
> # SPDX-License-Identifier: GPL-2.0
>
> set -e
> -set -o pipefail
>
> # To debug, uncomment the following line
> # set -x
> diff --git a/arch/powerpc/tools/gcc-check-mprofile-kernel.sh b/arch/powerpc/tools/gcc-check-mprofile-kernel.sh
> index 73e331e7660e..6193b0ed0c77 100755
> --- a/arch/powerpc/tools/gcc-check-mprofile-kernel.sh
> +++ b/arch/powerpc/tools/gcc-check-mprofile-kernel.sh
> @@ -2,7 +2,6 @@
> # SPDX-License-Identifier: GPL-2.0
>
> set -e
> -set -o pipefail
>
> # To debug, uncomment the following line
> # set -x
Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
This bug manifests when automated scripts expect to run a kernel build
after `make olddefconfig`. I reported this to Jan when I found that
kpatch-build [1] instances were hanging (expecting to hear from a user
that would never answer :(
[1] https://github.com/dynup/kpatch/blob/master/kpatch-build/kpatch-build
--
Joe
prev parent reply other threads:[~2025-08-28 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 9:54 [PATCH] powerpc/tools: drop `-o pipefail` in gcc check scripts Jan Stancek
2025-08-28 13:32 ` Joe Lawrence [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=0ab92ae3-674f-445e-883c-0e511add85d2@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).