From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Vasileios Almpanis via ltp" <ltp@lists.linux.it>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] pidns32: fix PID namespace nesting depth off-by-one
Date: Mon, 30 Mar 2026 10:23:11 +0000 [thread overview]
Message-ID: <69ca4f0f.df0a0220.131966.a7bf@mx.google.com> (raw)
In-Reply-To: <20260330100750.858390-1-vasileios.almpanis@virtuozzo.com>
Hi Vasileios,
> - if (tst_atomic_inc(level) == MAXNEST)
> + if (tst_atomic_load(level) == MAXNEST)
> return cpid;
>
> + tst_atomic_inc(level);
Makes sense, the old code incremented before checking, so the counter
hit 32 after only 31 clones. Splitting load and increment fixes it.
Reviewed-by: Andrea Cervesato <andrea.cervesato@suse.com>
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-30 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:07 [LTP] [PATCH] pidns32: fix PID namespace nesting depth off-by-one Vasileios Almpanis via ltp
2026-03-30 10:23 ` Andrea Cervesato via ltp [this message]
2026-03-30 13:33 ` Petr Vorel
2026-03-30 14:42 ` Cyril Hrubis
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=69ca4f0f.df0a0220.131966.a7bf@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.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