From: Ingo Molnar <mingo@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Rob Herring <robh@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: remove the target in signal traps when interrupted
Date: Sun, 7 Aug 2022 11:39:46 +0200 [thread overview]
Message-ID: <Yu+IYuGUAajZVnUF@gmail.com> (raw)
In-Reply-To: <20220807004809.69076-1-masahiroy@kernel.org>
* Masahiro Yamada <masahiroy@kernel.org> wrote:
> Reported-by: Ingo Molnar <mingo@kernel.org>
> Reported-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> If you are happy to help test this patch, that will be appreciated.
>
> Without applying this patch,
>
> $ make -j<nr-proc> 2>&1 | tee log
>
> Then, you will see an error reported in [1].
> You may need to repeat it dozen of times to reproduce it.
> The more CPU cores you have, the easier you will get the error.
>
> Apply this patch, and repeat the same.
> You will no longer see that error (hopefully).
>
>
> scripts/Kbuild.include | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
I've tested your patch on a system with 64 CPUs on the latest upstream
kernel, and without your patch I was able to quickly reproduce the
corrupted .cmd files within 4-5 interrupted kernel builds:
fs/xfs/libxfs/.xfs_alloc.o.cmd:5: *** unterminated call to function 'wildcard': missing ')'. Stop.
or:
kernel/time/.tick-broadcast.o.cmd:5: *** unterminated call to function 'wildcard': missing ')'. Stop.
or:
lib/.is_single_threaded.o.cmd:5: *** unterminated call to function 'wildcard': missing ')'. Stop.
These corrupted .cmd files blocked subsequent additive builds perpetually,
until I manually removed the corrupted .o.cmd file or did an explicit 'make clean'.
With your patch I've yet to see a single failure, after dozens of attempts.
Tested-by: Ingo Molnar <mingo@kernel.org>
Thanks a lot for taking care of this problem!
Ingo
next prev parent reply other threads:[~2022-08-07 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 0:48 [PATCH] kbuild: remove the target in signal traps when interrupted Masahiro Yamada
2022-08-07 9:39 ` Ingo Molnar [this message]
2022-08-19 4:37 ` 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=Yu+IYuGUAajZVnUF@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=robh@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.