All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: Michal Koutny <mkoutny@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] memcg_control_test: Disable swapping in test cgroup
Date: Thu, 27 Mar 2025 12:11:06 +0100	[thread overview]
Message-ID: <20250327111106.GA77751@pevik> (raw)
In-Reply-To: <20250326223532.3411149-1-tjmercier@google.com>

Hi,

> memcg_control_test_1 sets both a memory limit and a memsw/swap limit to
> a single page, and then asks mem_process to allocate 2 pages in an
> attempt to cause a memcg OOM kill. However, if swapping is enabled the
> first page can be swapped before the second is allocated causing neither
> limit to be exceeded, and no OOM kill to occur which results in a test
> failure. Fix this by disabling swap in the test cgroup if it is enabled,
> causing both pages to always be accounted under the same counter such
> that memory.max (v2) / memory.limit_in_bytes (v1) causes an OOM kill.

LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>

I suppose the old shell tests which cgroupv1 memory.memsw.limit_in_bytes are
written to test memory limits, thus only this one is suitable to modify.

The new C based tests (cgroupv2) should not be affected either.

Kind regards,
Petr

> Fixes: c0b815736 ("New testcase added by Naufal.")
> Signed-off-by: T.J. Mercier <tjmercier@google.com>
> ---
>  .../kernel/controllers/memcg/control/memcg_control_test.sh   | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)

> diff --git a/testcases/kernel/controllers/memcg/control/memcg_control_test.sh b/testcases/kernel/controllers/memcg/control/memcg_control_test.sh
> index 68287a70c..eb8db3e30 100644
> --- a/testcases/kernel/controllers/memcg/control/memcg_control_test.sh
> +++ b/testcases/kernel/controllers/memcg/control/memcg_control_test.sh
> @@ -12,7 +12,6 @@ TST_NEEDS_TMPDIR=1

>  PAGE_SIZE=$(tst_getconf PAGESIZE)

> -TOT_MEM_LIMIT=$PAGE_SIZE
>  ACTIVE_MEM_LIMIT=$PAGE_SIZE
>  PROC_MEM=$((PAGE_SIZE * 2))

> @@ -50,13 +49,13 @@ test1()

>  	# If the kernel is built without swap, the $memsw_memory_limit file is missing
>  	if [ -e "$test_dir/$memsw_memory_limit" ]; then
> -		ROD echo "$TOT_MEM_LIMIT" \> "$test_dir/$memsw_memory_limit"
> +		ROD echo 0 \> "$test_dir/$memsw_memory_limit"
>  	fi

>  	KILLED_CNT=0
>  	test_proc_kill

> -	if [ $PROC_MEM -gt $TOT_MEM_LIMIT ] && [ $KILLED_CNT -eq 0 ]; then
> +	if [ $KILLED_CNT -eq 0 ]; then
>  		tst_res TFAIL "Test #1: failed"
>  	else
>  		tst_res TPASS "Test #1: passed"

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 22:35 [LTP] [PATCH] memcg_control_test: Disable swapping in test cgroup T.J. Mercier via ltp
2025-03-27 11:11 ` Petr Vorel [this message]
     [not found] ` <lo4sjpn6uvhyhgi7welsp4dsvi6jxrl4h5gwacuvqmgfvfqcq7@ayoafjktxzyc>
2025-03-27 19:37   ` T.J. Mercier via ltp
  -- strict thread matches above, loose matches on Subject: below --
2025-03-26  4:11 T.J. Mercier via ltp

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=20250327111106.GA77751@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mkoutny@suse.com \
    --cc=tjmercier@google.com \
    /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.