linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Guopeng Zhang <zhangguopeng@kylinos.cn>
Cc: shuah@kernel.org, muchun.song@linux.dev, mkoutny@suse.com,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	shakeel.butt@linux.dev, linux-kernel@vger.kernel.org,
	tj@kernel.org, hannes@cmpxchg.org, mhocko@kernel.org,
	roman.gushchin@linux.dev,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 2/3] selftests: cgroup: make test_memcg_sock robust against delayed sock stats
Date: Thu, 27 Nov 2025 18:55:37 +0800	[thread overview]
Message-ID: <8ce13061-b4a7-4474-9e57-bab9b1a62b63@linux.dev> (raw)
In-Reply-To: <20251124123816.486164-3-zhangguopeng@kylinos.cn>



On 2025/11/24 20:38, Guopeng Zhang 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>
> ---
>   .../selftests/cgroup/test_memcontrol.c        | 20 ++++++++++++++++++-
>   1 file changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/cgroup/test_memcontrol.c b/tools/testing/selftests/cgroup/test_memcontrol.c
> index 4e1647568c5b..dda12e5c6457 100644
> --- a/tools/testing/selftests/cgroup/test_memcontrol.c
> +++ b/tools/testing/selftests/cgroup/test_memcontrol.c
> @@ -21,6 +21,8 @@
>   #include "kselftest.h"

This patch fails to apply to mm-new ...

Hmm, it expects #include "kselftest.h" here, but the tree uses
#include "../kselftest.h".

Which is odd, as that line hasn't been touched in years ...


  reply	other threads:[~2025-11-27 10:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 12:38 [PATCH v4 0/3] selftests: cgroup: Enhance robustness with polling helpers Guopeng Zhang
2025-11-24 12:38 ` [PATCH v4 1/3] selftests: cgroup: Add cg_read_key_long_poll() to poll a cgroup key with retries Guopeng Zhang
2025-12-02 19:24   ` Shakeel Butt
2025-11-24 12:38 ` [PATCH v4 2/3] selftests: cgroup: make test_memcg_sock robust against delayed sock stats Guopeng Zhang
2025-11-27 10:55   ` Lance Yang [this message]
2025-11-27 11:18     ` Guopeng Zhang
2025-11-27 11:29       ` Lance Yang
2025-12-02 23:12   ` Shakeel Butt
2025-12-03  3:27     ` Guopeng Zhang
2025-11-24 12:38 ` [PATCH v4 3/3] selftests: cgroup: Replace sleep with cg_read_key_long_poll() for waiting on nr_dying_descendants Guopeng Zhang
2025-12-02 23:18   ` Shakeel Butt
2025-12-03  3:32     ` Guopeng Zhang
2025-12-02  5:45 ` [PATCH v4 0/3] selftests: cgroup: Enhance robustness with polling helpers Tejun Heo

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=8ce13061-b4a7-4474-9e57-bab9b1a62b63@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.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 \
    --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