OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>,
	Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/2] sched: Fix incorrect nproc report inside CT
Date: Wed, 28 Oct 2026 16:16:08 +0100	[thread overview]
Message-ID: <05214d32-983e-42de-9b7c-e8778902ee4b@virtuozzo.com> (raw)
In-Reply-To: <20261028-ct-invalid-nrpoc-v2-0-968fe985ce27@virtuozzo.com>

Looks good. (except that sashiko reveiw should be handled)

Reviewed-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>

On 10/28/26 13:46, Vladimir Riabchun wrote:
> We observed weird nproc behavior - it reported 64 CPUs
> no matter what the CT limits were or how many CPUs the host
> actually had.
> 
> nproc code uses sched_getaffinity syscall under the hood[1].
> It appears that this syscall returned complete nonsence when
> called from VE - we ignored both num_online_vcpus and
> cgroup cpuset limitations.
> 
> Now it is fixed and a new selftest is added.
> 
> [1]: https://github.com/coreutils/gnulib/blob/master/lib/nproc.c#L144
> https://virtuozzo.atlassian.net/browse/VSTOR-141682
> 
> Signed-off-by: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
> ---
> Changes in v2:
> - Updated vCPU logic in patch 1. Now we don't return actual
>   cpumask, insted first min(vcpu, count(mask)) bits are set.
>   This is closer to the real CT resources.
> - Patch 2: adjusted logic and added one more test.
> - Link to v1: http://lore.virtuozzo.com/20261027-ct-invalid-nrpoc-v1-0-48727c3afe16@virtuozzo.com
> 
> ---
> Vladimir Riabchun (2):
>       sched: Fix sched_getaffinity syscall
>       selftests: ve: Test sched_getaffinity in VE
> 
>  kernel/sched/syscalls.c                            |  18 +-
>  tools/testing/selftests/ve/.gitignore              |   1 +
>  tools/testing/selftests/ve/Makefile                |   1 +
>  .../selftests/ve/ve_sched_getaffinity_test.c       | 213 +++++++++++++++++++++
>  4 files changed, 228 insertions(+), 5 deletions(-)
> ---
> base-commit: a1c0fd720976500f854fd5a4c946a54e65c82d78
> change-id: 20261027-ct-invalid-nrpoc-f183b3ba691d
> 
> Best regards,
> --  
> Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>

-- 
Best regards, Pavel Tikhomirov
Senior Software Developer, Virtuozzo.

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-10-28 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 12:46 Vladimir Riabchun
2026-10-28 12:46 ` [Devel] [PATCH hci-8.1 v2 1/2] sched: Fix sched_getaffinity syscall Vladimir Riabchun
2026-10-28 12:50   ` no-reply
2026-10-28 21:14     ` Vladimir Riabchun
2026-10-28 12:46 ` [Devel] [PATCH hci-8.1 v2 2/2] selftests: ve: Test sched_getaffinity in VE Vladimir Riabchun
2026-10-28 12:51   ` no-reply
2026-10-28 21:29     ` Vladimir Riabchun
2026-10-28 15:16 ` Pavel Tikhomirov [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=05214d32-983e-42de-9b7c-e8778902ee4b@virtuozzo.com \
    --to=ptikhomirov@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=khorenko@virtuozzo.com \
    --cc=vladimir.riabchun@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