Skip to content

Commit 6360d44

Browse files
Guopeng Zhanghtejun
authored andcommitted
selftests: cgroup: make test_memcg_sock robust against delayed sock stats
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> Acked-by: Michal Koutný <mkoutny@suse.com> Signed-off-by: Tejun Heo <tj@kernel.org>
1 parent 311ead1 commit 6360d44

1 file changed

Lines changed: 19 additions & 1 deletion

File tree

tools/testing/selftests/cgroup/test_memcontrol.c

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@
2121
#include "kselftest.h"
2222
#include "cgroup_util.h"
2323

24+
#define MEMCG_SOCKSTAT_WAIT_RETRIES 30
25+
2426
static bool has_localevents;
2527
static bool has_recursiveprot;
2628

@@ -1384,6 +1386,7 @@ static int test_memcg_sock(const char *root)
13841386
int bind_retries = 5, ret = KSFT_FAIL, pid, err;
13851387
unsigned short port;
13861388
char *memcg;
1389+
long sock_post = -1;
13871390

13881391
memcg = cg_name(root, "memcg_test");
13891392
if (!memcg)
@@ -1432,7 +1435,22 @@ static int test_memcg_sock(const char *root)
14321435
if (cg_read_long(memcg, "memory.current") < 0)
14331436
goto cleanup;
14341437

1435-
if (cg_read_key_long(memcg, "memory.stat", "sock "))
1438+
/*
1439+
* memory.stat is updated asynchronously via the memcg rstat
1440+
* flushing worker, which runs periodically (every 2 seconds,
1441+
* see FLUSH_TIME). On a busy system, the "sock " counter may
1442+
* stay non-zero for a short period of time after the TCP
1443+
* connection is closed and all socket memory has been
1444+
* uncharged.
1445+
*
1446+
* Poll memory.stat for up to 3 seconds (~FLUSH_TIME plus some
1447+
* scheduling slack) and require that the "sock " counter
1448+
* eventually drops to zero.
1449+
*/
1450+
sock_post = cg_read_key_long_poll(memcg, "memory.stat", "sock ", 0,
1451+
MEMCG_SOCKSTAT_WAIT_RETRIES,
1452+
DEFAULT_WAIT_INTERVAL_US);
1453+
if (sock_post)
14361454
goto cleanup;
14371455

14381456
ret = KSFT_PASS;

0 commit comments

Comments
 (0)