From: Li Wang via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/2] pidns32: fix PID namespace nesting depth off-by-one
Date: Fri, 3 Apr 2026 09:58:56 +0800 [thread overview]
Message-ID: <ac8e4A9YPcXoFobL@redhat.com> (raw)
In-Reply-To: <20260402205534.224141-3-pvorel@suse.cz>
On Thu, Apr 02, 2026 at 10:55:34PM +0200, Petr Vorel wrote:
> From: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
>
> The 2023 refactor used tst_atomic_inc() before clone with a zero-initial
> counter, which only performed 31 CLONE_NEWPID nests while still expecting
> MAXNEST (32). Use tst_atomic_return_add() so the shared counter runs
> 0..32 and the chain reaches 32 nested namespaces again.
>
> Fixes: 647cfd468c3b ("Refactor pidns32 test using new LTP API")
> Reviewed-by: Andrea Cervesato <andrea.cervesato@suse.com>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
> [ pvorel: use tst_atomic_return_add() ]
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Reviewed-by: Li Wang <liwang@redhat.com>
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-03 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 20:55 [LTP] [PATCH v2 0/2] pidns32: fix PID namespace nesting depth off-by-one Petr Vorel
2026-04-02 20:55 ` [LTP] [PATCH v2 1/2] tst_atomic: Add tst_atomic_return_add() Petr Vorel
2026-04-03 1:58 ` Li Wang via ltp
2026-04-07 11:54 ` Cyril Hrubis
2026-04-02 20:55 ` [LTP] [PATCH v2 2/2] pidns32: fix PID namespace nesting depth off-by-one Petr Vorel
2026-04-03 1:58 ` Li Wang via ltp [this message]
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=ac8e4A9YPcXoFobL@redhat.com \
--to=ltp@lists.linux.it \
--cc=liwang@redhat.com \
--cc=pvorel@suse.cz \
--cc=vasileios.almpanis@virtuozzo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox