From: Li Wang <li.wang@linux.dev>
To: akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@kernel.org,
roman.gushchin@linux.dev, shakeel.butt@linux.dev,
muchun.song@linux.dev, tj@kernel.org, mkoutny@suse.com,
shuah@kernel.org
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] selftests/cgroup: Fix false positive failures in test_percpu_basic
Date: Fri, 1 May 2026 10:20:56 +0800 [thread overview]
Message-ID: <20260501022058.18024-1-li.wang@linux.dev> (raw)
This patch series addresses two separate issues that cause false
positive failures in the test_percpu_basic test within the cgroup
kmem selftests.
The first issue stems from a hardcoded assumption about the system
page size, which breaks the test on architectures with larger page
sizes.
The second issue is an overly strict memory check that fails to
account for the slab metadata allocated during cgroup creation.
v2:
* Replace my email with li.wang@linux.dev
* Adding Waiman's Reviewed-by tag
Li Wang (2):
selftests/cgroup: Fix hardcoded page size in test_percpu_basic
selftests/cgroup: include slab in test_percpu_basic memory check
tools/testing/selftests/cgroup/test_kmem.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-01 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 2:20 Li Wang [this message]
2026-05-01 2:20 ` [PATCH v2 1/2] selftests/cgroup: Fix hardcoded page size in test_percpu_basic Li Wang
2026-05-06 12:10 ` Sayali Patil
2026-05-01 2:20 ` [PATCH v2 2/2] selftests/cgroup: include slab in test_percpu_basic memory check Li Wang
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=20260501022058.18024-1-li.wang@linux.dev \
--to=li.wang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
/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