I didn't see this come back from the list and it was sent
45 minutes ago (vs. other emails of mine that have come
back in under a minute).
Did anyone else see it? Sorry for the repeat if it did.
FWIW, the below is from the publicly posted change notes
for the 5.2.3 patch.
-------- Original Message --------
Subject: valid kernel patch? using -e to catch errors?
Date: Mon, 29 Jul 2019 00:16:56 -0700
To: bug-bash <bug-bash@gnu.org>
I wonder if this patch that went into the linux kernel, 5.2.3, will do what
they think it will since posix changed the meaning.
If not, maybe Greg should go over and explain it to them!
commit df324bab425f70bf2a1d11f5880c88940b7e403d
Author: Masahiro Yamada <yamada.masah...@socionext.com>
Date: Tue Jun 25 16:26:22 2019 +0900
x86/build: Add 'set -e' to mkcapflags.sh to delete broken capflags.c
[ Upstream commit bc53d3d777f81385c1bb08b07bd1c06450ecc2c1 ]
Without 'set -e', shell scripts continue running even after any
error occurs. The missed 'set -e' is a typical bug in shell scripting.
For example, when a disk space shortage occurs while this script is
running, it actually ends up with generating a truncated capflags.c.
Yet, mkcapflags.sh continues running and exits with 0. So, the build
system assumes it has succeeded.
It will not be re-generated in the next invocation of Make since its
timestamp is newer than that of any of the source files.
Add 'set -e' so that any error in this script is caught and propagated
to the build system.
Since 9c2af1c7377a ("kbuild: add .DELETE_ON_ERROR special target"),
make automatically deletes the target on any failure. So, the broken
capflags.c will be deleted automatically.
Signed-off-by: Masahiro Yamada <yamada.masah...@socionext.com>
Signed-off-by: Thomas Gleixner <t...@linutronix.de>
Cc: "H. Peter Anvin" <h...@zytor.com>
Cc: Borislav Petkov <b...@alien8.de>
Link:
https://lkml.kernel.org/r/20190625072622.17679-1-yamada.masah...@socionext.com
Signed-off-by: Sasha Levin <sas...@kernel.org>
