All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Attila Fazekas <afazekas@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] mmap22: Bound child memory allocation to avoid OOM
Date: Tue, 3 Nov 2026 21:14:10 +0100	[thread overview]
Message-ID: <20261103201410.GB154873@pevik> (raw)
In-Reply-To: <20261102105704.1577364-1-afazekas@redhat.com>

Hi Attila,

> Currently, stress_child() allocates memory in an infinite loop without
> bounds. Under memory pressure, once the cgroup memory limit is reached
> and the parent's droppable pages are reclaimed, the child continues
> allocating non-droppable heap memory. This eventually exhausts the cgroup
> limit and triggers the cgroup OOM killer, terminating either the child or
> the test parent process.

> Fix this by bounding the child's allocation to CHILD_ALLOC_MAX
> (ALLOC_SIZE + 32MB). The total requested memory (128MB parent + 160MB
> child = 288MB) exceeds the 256MB cgroup limit by 32MB, which reliably
> forces the kernel to reclaim MAP_DROPPABLE pages. Once CHILD_ALLOC_MAX is
> reached, the child calls pause() to keep memory resident. Since 160MB is
> well below the 256MB cgroup limit, non-droppable memory alone cannot
> trigger an OOM.

LGTM, but it'd be nice if somebody else double check.
Reviewed-by: Petr Vorel <pvorel@suse.cz>

Kind regards,
Petr

> Assisted-by: Gemini CLI
> Signed-off-by: Attila Fazekas <afazekas@redhat.com>
> ---
>  testcases/kernel/syscalls/mmap/mmap22.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)

> diff --git a/testcases/kernel/syscalls/mmap/mmap22.c b/testcases/kernel/syscalls/mmap/mmap22.c
> index 0b95c578f..16fcb6dd8 100644
> --- a/testcases/kernel/syscalls/mmap/mmap22.c
> +++ b/testcases/kernel/syscalls/mmap/mmap22.c
> @@ -26,6 +26,7 @@

>  #define MEM_LIMIT (256 * TST_MB)
>  #define ALLOC_SIZE (128 * TST_MB)
> +#define CHILD_ALLOC_MAX (ALLOC_SIZE + 32 * TST_MB)

>  static struct tst_cg_group *cg_child;
>  static pid_t child;
> @@ -33,13 +34,15 @@ static int page_size;

>  static void stress_child(void)
>  {
> -	for (;;) {
> +	for (size_t sz = 0; sz < CHILD_ALLOC_MAX; sz += page_size) {
>  		char *buf = malloc(page_size);

>  		if (!buf)
> -			exit(1);
> +			break;
>  		memset(buf, 'B', page_size);
>  	}
> +
> +	pause();
>  }

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

  parent reply	other threads:[~2026-11-03 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 10:57 [LTP] [PATCH] mmap22: Bound child memory allocation to avoid OOM Attila Fazekas via ltp
2026-11-02 18:54 ` [LTP] " linuxtestproject.agent
2026-11-03 20:14 ` Petr Vorel [this message]
2026-11-04 16:32 ` [LTP] [PATCH] " Cyril Hrubis
2026-11-05  8:04   ` Attila Fazekas 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=20261103201410.GB154873@pevik \
    --to=pvorel@suse.cz \
    --cc=afazekas@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.