From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
mm-commits@vger.kernel.org, vbabka@suse.cz, tj@kernel.org,
shakeelb@google.com, mhocko@kernel.org, longman@redhat.com,
hannes@cmpxchg.org, cl@linux.com, li.wang@linux.dev
Subject: Re: + selftests-cgroup-fix-hardcoded-page-size-in-test_percpu_basic.patch added to mm-new branch
Date: Fri, 1 May 2026 16:59:56 -0700 [thread overview]
Message-ID: <20260501235956.146285-1-sj@kernel.org> (raw)
In-Reply-To: <20260501123547.779FCC2BCB4@smtp.kernel.org>
On Fri, 01 May 2026 05:35:46 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> The patch titled
> Subject: selftests/cgroup: fix hardcoded page size in test_percpu_basic
> has been added to the -mm mm-new branch. Its filename is
> selftests-cgroup-fix-hardcoded-page-size-in-test_percpu_basic.patch
[...]
> ------------------------------------------------------
> From: Li Wang <li.wang@linux.dev>
> Subject: selftests/cgroup: fix hardcoded page size in test_percpu_basic
> Date: Fri, 1 May 2026 10:20:57 +0800
>
> Patch series "selftests/cgroup: Fix false positive failures in
> test_percpu_basic", v2.
>
> 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.
>
>
> Thi patch (of 2):
Nit. s/Thi/This/
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-01 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 12:35 + selftests-cgroup-fix-hardcoded-page-size-in-test_percpu_basic.patch added to mm-new branch Andrew Morton
2026-05-01 23:59 ` SeongJae Park [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=20260501235956.146285-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=li.wang@linux.dev \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=vbabka@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.