[Buildroot] [PATCH] check-kernel-headers.sh: use a trap to remove the temporary file

unixmania at gmail.com unixmania at gmail.com
Tue Sep 24 02:49:40 UTC 2019

From: Carlos Santos <unixmania at gmail.com>

The POSIX specification defines a 'trap <action> EXIT' mechanism that is
useful to perform clean-up actions in shell scripts. A trap has two main
advantages over hand-crafted clean-up mechanisms:

- It runs even if the process is terminated by a SIGTERM.
- It runs even if the script stops due to a pipeline failure (set -e).

Now we can make the script to stop immediately if a compilation error
occurs, instead of letting it try to run an unexisting program.

This change may appear to be overkill but Buildroot is an open source
project and each piece of code is a potential learning tool for other
developments. We must strive to provide good examples.

Signed-off-by: Carlos Santos <unixmania at gmail.com>
 support/scripts/check-kernel-headers.sh | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/support/scripts/check-kernel-headers.sh b/support/scripts/check-kernel-headers.sh
index a8b94f6a02..970e5abf9e 100755
--- a/support/scripts/check-kernel-headers.sh
+++ b/support/scripts/check-kernel-headers.sh
@@ -9,6 +9,14 @@ HDR_M="${HDR_VER%%.*}"
+# Exit on any error, so we don't try to run an unexisting program if the
+# compilation fails.
+set -e
+# Set the clean-up trap in advance to prevent a race condition in which we
+# create the file but get a SIGTERM before setting it.
+trap '[ -n "${EXEC}" ] && rm -f "${EXEC}"' EXIT
 EXEC="$(mktemp -p "${BUILDDIR}" -t .check-headers.XXXXXX)"
 # We do not want to account for the patch-level, since headers are
@@ -33,10 +41,8 @@ int main(int argc __attribute__((unused)),
         return 1;
     return 0;
+    etaporra
-rm -f "${EXEC}"
-exit ${ret}

More information about the buildroot mailing list