public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH] seccomp: Make seccomp.sh re-entrancy safe
Date: Wed, 21 Jun 2023 14:51:27 +1000	[thread overview]
Message-ID: <ZJKBz9WVOkmLPFkJ@zatzit> (raw)
In-Reply-To: <20230621030637.640272-1-david@gibson.dropbear.id.au>

[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]

On Wed, Jun 21, 2023 at 01:06:37PM +1000, David Gibson wrote:
> seccomp.sh generates seccomp.h piece by piece using >> directives.  This
> means that if two instances of seccomp.h are run concurrently a corrupted
> version of seccomp.h will be generated. Amongst other problems this can
> cause spurious failures on clang-tidy.
> 
> Alter seccomp.sh to build the output in a temporary file and atomic move it
> to seccomp.h, so concurrent invocations will still result in valud output.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

A note on context: I discovered this while working on the Avocado
stuff: avocado would run "make cppcheck" and "make clang-tidy" in
parallel, since both require seccomp.h to be generated, they'd both
try to generate it at the same time, and it would blow up.

> ---
>  seccomp.sh | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/seccomp.sh b/seccomp.sh
> index 092c24e0..e1224e0d 100755
> --- a/seccomp.sh
> +++ b/seccomp.sh
> @@ -15,7 +15,7 @@
>  
>  TMP="$(mktemp)"
>  IN="$@"
> -OUT="seccomp.h"
> +OUT="$(mktemp)"
>  
>  [ -z "${ARCH}" ] && ARCH="$(uname -m)"
>  [ -z "${CC}" ] && CC="cc"
> @@ -53,7 +53,7 @@ BST='	BPF_JUMP(BPF_JMP | BPF_JGE | BPF_K, @NR@, @R@, @L@),'
>  
>  # cleanup() - Remove temporary file if it exists
>  cleanup() {
> -	rm -f "${TMP}"
> +	rm -f "${TMP}" "${OUT}"
>  }
>  trap "cleanup" EXIT
>  
> @@ -254,3 +254,5 @@ for __p in ${__profiles}; do
>  
>  	gen_profile "${__p}" ${__calls}
>  done
> +
> +mv "${OUT}" seccomp.h

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-21  5:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  3:06 [PATCH] seccomp: Make seccomp.sh re-entrancy safe David Gibson
2023-06-21  4:51 ` David Gibson [this message]
2023-06-26  7:22 ` Stefano Brivio

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=ZJKBz9WVOkmLPFkJ@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).