From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/1] lib: Retry safe_clone() on ENOSPC|EUSERS
Date: Wed, 30 Mar 2022 14:29:14 +0200 [thread overview]
Message-ID: <YkRNGt435X50u8Z9@yuki> (raw)
In-Reply-To: <20220328204643.2601-1-pvorel@suse.cz>
Hi!
> In some tests we are creating the namespaces faster than they are being
> asynchronously cleaned up in the kernel:
>
> $ sudo ./userns08 -i 10
> userns08.c:65: TPASS: Denied write access to ./restricted : EACCES (13)
> userns08.c:65: TPASS: Denied write access to ./restricted : EACCES (13)
> userns08.c:65: TPASS: Denied write access to ./restricted : EACCES (13)
> userns08.c:65: TPASS: Denied write access to ./restricted : EACCES (13)
> userns08.c:65: TPASS: Denied write access to ./restricted : EACCES (13)
> userns08.c:36: TBROK: clone3 failed: ENOSPC (28)
>
> Thus retrying the clone() on ENOSPC (or EUSERS for kernel < 4.9).
>
> Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> changes v1->v2:
> * use TST_RETRY_FN_EXP_BACKOFF() (Cyril)
>
> NOTE: 0.1s seems to be safe, although using TST_RETRY_FUNC() with 1s
> (the default) would be of course OK.
I would just put in the default 1s to make things extra safe even on
slow hardware.
> lib/tst_test.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/lib/tst_test.c b/lib/tst_test.c
> index 384c73e163..2e89d954ec 100644
> --- a/lib/tst_test.c
> +++ b/lib/tst_test.c
> @@ -436,6 +436,9 @@ pid_t safe_fork(const char *filename, unsigned int lineno)
> return pid;
> }
>
> +/* too fast creating namespaces => retrying */
> +#define TST_CHECK_ENOSPC(x) ((x) >= 0 || !(errno == ENOSPC || errno == EUSERS))
Reading the manual page I do not think that we have to retry on EUSERS,
that used to be the return value where we reached limit of nested
namespaces and that is not going go away if we retry.
Otherwise the rest looks good.
> pid_t safe_clone(const char *file, const int lineno,
> const struct tst_clone_args *args)
> {
> @@ -444,7 +447,7 @@ pid_t safe_clone(const char *file, const int lineno,
> if (!tst_test->forks_child)
> tst_brk(TBROK, "test.forks_child must be set!");
>
> - pid = tst_clone(args);
> + pid = TST_RETRY_FN_EXP_BACKOFF(tst_clone(args), TST_CHECK_ENOSPC, 0.1);
>
> switch (pid) {
> case -1:
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-30 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 20:46 [LTP] [PATCH v2 1/1] lib: Retry safe_clone() on ENOSPC|EUSERS Petr Vorel
2022-03-30 12:29 ` Cyril Hrubis [this message]
2022-03-30 12:46 ` pvorel
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=YkRNGt435X50u8Z9@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.