public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] mmap22.c: Test for new MAP_DROPPABLE flag for mmap
Date: Fri, 25 Apr 2025 13:40:06 +0200	[thread overview]
Message-ID: <aAt0liEAJpTHbwek@yuki.lan> (raw)
In-Reply-To: <20250416191645.355088-1-wegao@suse.com>

Hi!
> +static void test_mmap(void)
> +{
> +	size_t alloc_size = ALLOC_SIZE;
> +	size_t page_size = getpagesize();
> +	void *alloc;
> +	pid_t child;
> +
> +	cg_child = tst_cg_group_mk(tst_cg, "child");
> +	SAFE_CG_PRINTF(tst_cg, "memory.max", "%d", MEM_LIMIT);
> +	SAFE_CG_PRINTF(cg_child, "cgroup.procs", "%d", getpid());
> +
> +	alloc = SAFE_MMAP(0, alloc_size, PROT_READ | PROT_WRITE,
> +			MAP_ANONYMOUS | MAP_DROPPABLE, -1, 0);
> +
> +	memset(alloc, 'A', alloc_size);
> +	for (size_t i = 0; i < alloc_size; i += page_size) {
> +		if (*(char *)(alloc + i) != 'A')
> +			tst_res(TFAIL, "memset failed");
> +	}
> +
> +	child = SAFE_FORK();
> +	if (!child) {
> +		for (;;)
> +			*(char *)malloc(page_size) = 'B';
> +	}
> +
> +	while (1) {
> +		for (size_t i = 0; i < alloc_size; i += page_size) {
> +			if (!tst_remaining_runtime())
> +				tst_brk(TBROK, "MAP_DROPPABLE did not drop memory within the timeout period.");

This should rather be tst_res(TFAIL, ...) followed by goto kill_child;

> +			if (!*(uint8_t *)(alloc + i)) {

We are casting the alloc pointer on each access, it would probably be
more reasonable to defined it as char * instead of void * and drop the
casts from the code.

> +				tst_res(TPASS, "MAP_DROPPABLE test pass.");
> +				goto kill_child;
> +			}
> +		}
> +	}
> +
> +kill_child:
> +	SAFE_KILL(child, SIGKILL);
> +	SAFE_WAITPID(child, NULL, 0);
> +	SAFE_MUNMAP(alloc, alloc_size);
> +}
> +
> +static void setup(void)
> +{
> +	void *addr = mmap(0, 1, PROT_READ | PROT_WRITE,
> +			MAP_ANONYMOUS | MAP_DROPPABLE, -1, 0);
> +	if (addr == MAP_FAILED && errno == EINVAL)
> +		tst_brk(TCONF, "MAP_DROPPABLE not support");

We are missing munmap() here in the case that addr != MAP_FAILED.


Other than these minor points the rest of the code looks good to me.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2025-04-25 11:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28 13:32 [LTP] [PATCH v1] mmap21.c: Test for new MAP_DROPPABLE flag for mmap Wei Gao via ltp
2024-12-31 10:04 ` Li Wang
2025-01-02  9:38   ` Cyril Hrubis
2025-01-03  1:42   ` Wei Gao via ltp
2025-01-03 13:54   ` Wei Gao via ltp
2025-01-03 13:56 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-03-10 16:18   ` Cyril Hrubis
2025-04-16 19:16   ` [LTP] [PATCH v3] mmap22.c: " Wei Gao via ltp
2025-04-25 11:40     ` Cyril Hrubis [this message]
2025-04-28 16:04     ` [LTP] [PATCH v4] " Wei Gao via ltp
2025-05-07 15:25       ` Cyril Hrubis
2025-05-12  8:43         ` Jan Stancek via ltp
2025-05-13 15:44           ` Wei Gao via ltp
2025-05-14  8:51             ` Jan Stancek via ltp
2025-05-14  9:04               ` Li Wang via ltp
2025-05-14  9:10                 ` Jan Stancek via ltp
2025-05-14  9:14                   ` Li Wang via ltp
2025-05-14 11:15                     ` Jan Stancek via ltp
2025-05-14 12:44                       ` Li Wang via ltp
2025-05-14 12:54                         ` Jan Stancek 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=aAt0liEAJpTHbwek@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=wegao@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox