From: "Michal Koutný" <mkoutny@suse.com>
To: Guopeng Zhang <zhangguopeng@kylinos.cn>
Cc: tj@kernel.org, hannes@cmpxchg.org, shuah@kernel.org,
roman.gushchin@linux.dev, lance.yang@linux.dev,
shakeel.butt@linux.dev, muchun.song@linux.dev,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] selftests: cgroup: make test_memcg_sock robust against delayed sock stats
Date: Thu, 4 Dec 2025 16:04:35 +0100 [thread overview]
Message-ID: <dyie6co47aemejhok5xjjmsvfjpsg2djmkbucnonent3afqylm@ojui2r4gb3ro> (raw)
In-Reply-To: <20251203115631.947908-3-zhangguopeng@kylinos.cn>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
On Wed, Dec 03, 2025 at 07:56:30PM +0800, Guopeng Zhang <zhangguopeng@kylinos.cn> wrote:
> test_memcg_sock() currently requires that memory.stat's "sock " counter
> is exactly zero immediately after the TCP server exits. On a busy system
> this assumption is too strict:
>
> - Socket memory may be freed with a small delay (e.g. RCU callbacks).
> - memcg statistics are updated asynchronously via the rstat flushing
> worker, so the "sock " value in memory.stat can stay non-zero for a
> short period of time even after all socket memory has been uncharged.
>
> As a result, test_memcg_sock() can intermittently fail even though socket
> memory accounting is working correctly.
>
> Make the test more robust by polling memory.stat for the "sock "
> counter and allowing it some time to drop to zero instead of checking
> it only once. The timeout is set to 3 seconds to cover the periodic
> rstat flush interval (FLUSH_TIME = 2*HZ by default) plus some
> scheduling slack. If the counter does not become zero within the
> timeout, the test still fails as before.
>
> On my test system, running test_memcontrol 50 times produced:
>
> - Before this patch: 6/50 runs passed.
> - After this patch: 50/50 runs passed.
>
> Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
> Suggested-by: Lance Yang <lance.yang@linux.dev>
> Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
> ---
> .../selftests/cgroup/test_memcontrol.c | 20 ++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
Acked-by: Michal Koutný <mkoutny@suse.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
next prev parent reply other threads:[~2025-12-04 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 11:56 [PATCH v5 0/3] selftests: cgroup: Enhance robustness with polling helpers Guopeng Zhang
2025-12-03 11:56 ` [PATCH v5 1/3] selftests: cgroup: Add cg_read_key_long_poll() to poll a cgroup key with retries Guopeng Zhang
2025-12-04 15:04 ` Michal Koutný
2025-12-03 11:56 ` [PATCH v5 2/3] selftests: cgroup: make test_memcg_sock robust against delayed sock stats Guopeng Zhang
2025-12-04 15:04 ` Michal Koutný [this message]
2025-12-03 11:56 ` [PATCH v5 3/3] selftests: cgroup: Replace sleep with cg_read_key_long_poll() for waiting on nr_dying_descendants Guopeng Zhang
2025-12-04 15:04 ` Michal Koutný
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=dyie6co47aemejhok5xjjmsvfjpsg2djmkbucnonent3afqylm@ojui2r4gb3ro \
--to=mkoutny@suse.com \
--cc=hannes@cmpxchg.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=zhangguopeng@kylinos.cn \
/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