public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] test: Remove race between commands run in the same context
Date: Thu, 6 Apr 2023 11:15:31 +1000	[thread overview]
Message-ID: <ZC4dMzMufrl6cMzf@yekko> (raw)
In-Reply-To: <20230405142324.75f0a416@elisabeth>

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

On Wed, Apr 05, 2023 at 02:23:24PM +0200, Stefano Brivio wrote:
> On Wed,  5 Apr 2023 11:56:42 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > context_run() has a race condition if two commands are run in close
> > proximity (generally involving at least one in the background).  Because we
> > always use the same name for the temporary fifo files, if another command
> > is issued while the fifos for the first still exist, mkfifo will fail,
> > typically causing the entire test script to jam.
> > 
> > Create unique names for the temporary fifos to avoid this problem.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> >  test/lib/context | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/test/lib/context b/test/lib/context
> > index d9d8260..09cad89 100644
> > --- a/test/lib/context
> > +++ b/test/lib/context
> > @@ -93,8 +93,8 @@ context_run() {
> >  	__name="$1"
> >  	__log="${LOGDIR}/context_${__name}.log"
> >  	__enter="${STATESETUP}/context_${__name}.enter"
> > -	__stdout="${STATESETUP}/context_${__name}.stdout"
> > -	__stderr="${STATESETUP}/context_${__name}.stderr"
> > +	__stdout="$(mktemp -u "${STATESETUP}/context_${__name}.stdout.XXXXXXXX")"
> > +	__stderr="$(mktemp -u "${STATESETUP}/context_${__name}.stderr.XXXXXXXX")"
> 
> In practice, this is never going to be an issue, but strictly
> speaking, -u doesn't guarantee the name is unique.

Yeah, I know.

> On the other hand we don't need a loop (or further directories) with
> this, so the simplicity of it might be preferable over correctness...

Right, that's the conclusion I came to as well.

-- 
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-04-06  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  1:56 [PATCH] test: Remove race between commands run in the same context David Gibson
2023-04-05 12:23 ` Stefano Brivio
2023-04-06  1:15   ` David Gibson [this message]
2023-04-07 23:13 ` 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=ZC4dMzMufrl6cMzf@yekko \
    --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).