public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Dennis Brendel <dbrendel@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] munlockall: add test case that verifies memory has been unlocked
Date: Thu, 7 Mar 2024 08:36:13 +0100	[thread overview]
Message-ID: <71084990-17ef-461e-907e-e2bc39c2b236@redhat.com> (raw)
In-Reply-To: <ZeiLMOR4rXMY7Sr4@yuki>

Hi Cyril,

On 3/6/24 16:26, Cyril Hrubis wrote:
> Hi!
>> +/*\
>> + * [Description]
>> + *
>> + * Verify that munlockall(2) unlocks all previously locked memory
>> + */
>>  
>> -char *TCID = "munlockall01";
>> -int TST_TOTAL = 1;
>> +#include <sys/mman.h>
>>  
>> -#if !defined(UCLINUX)
>> +#include "tst_test.h"
>>  
>> -int main(int ac, char **av)
>> +static void verify_munlockall(void)
>>  {
>> -	int lc;
>> -
>> -	tst_parse_opts(ac, av, NULL, NULL);
>> +	unsigned long size = 0;
>>  
>> -	setup();
>> +	SAFE_FILE_LINES_SCANF("/proc/self/status", "VmLck: %ld", &size);
>>  
>> -	/* check looping state */
>> -	for (lc = 0; TEST_LOOPING(lc); lc++) {
>> +	if (size != 0UL)
>> +		tst_brk(TBROK, "Locked memory after init should be 0 but is %ld", size);
>>  
>> -		tst_count = 0;
>> +	if (mlockall(MCL_CURRENT | MCL_FUTURE) != 0)
>> +		tst_brk(TBROK | TERRNO, "Could not lock memory using mlockall()");
>>  
>> -		TEST(munlockall());
>> +	SAFE_FILE_LINES_SCANF("/proc/self/status", "VmLck: %ld", &size);
>>  
>> -		/* check return code */
>> -		if (TEST_RETURN == -1) {
>> -			tst_resm(TFAIL | TTERRNO, "munlockall() Failed with"
>> -				 " return=%ld", TEST_RETURN);
>> -		} else {
>> -			tst_resm(TPASS, "munlockall() passed with"
>> -				 " return=%ld ", TEST_RETURN);
>> +	if (size == 0UL)
>> +		tst_brk(TBROK, "Locked memory after mlockall() should be greater than 0, "
>> +			       "but is %ld", size);
> 
> This line can be shorter:
> 
> 	tst_brk(TBROK, "After mlockall() locked memory should be >0");
> 
> We already checked that size is 0 so no need to print it.

Agreed :-)

>> -		}
>> -	}
>> +	if (munlockall() != 0)
>> +		tst_brk(TBROK | TERRNO, "Could not unlock memory using munlockall()");
> 
> We are testing the munlockall() syscall here so it would be better to
> use the TST_EXP_PASS() macro.

The actual purpose of the test was not checking the return value of the syscall
(wrapper), but the behavior as reported by the kernel through /proc - but fair
enough, it does not do any harm :-)

>> -	/* cleanup and exit */
>> -	cleanup();
>> -	tst_exit();
>> +	SAFE_FILE_LINES_SCANF("/proc/self/status", "VmLck: %ld", &size);
>>  
>> +	if (size != 0UL)
>> +		tst_res(TFAIL, "Locked memory after munlockall() should be 0 but is %ld", size);
>> +
>> +	else
>> +		tst_res(TPASS, "Memory successfully locked and unlocked");
>>  }
>>  
>> -#else
>> -
>> -int main(void)
>> -{
>> -	tst_resm(TINFO, "test is not available on uClinux");
>> -	tst_exit();
>> -}
>> -
>> -#endif /* if !defined(UCLINUX) */
>> -
>> -/* setup() - performs all ONE TIME setup for this test. */
>> -void setup(void)
>> -{
>> -	tst_require_root();
>> -
>> -	tst_sig(NOFORK, DEF_HANDLER, cleanup);
>> -
>> -	TEST_PAUSE;
>> -}
>> -
>> -/*
>> - * cleanup() - performs all ONE TIME cleanup for this test at
>> - *		completion or premature exit.
>> - */
>> -void cleanup(void)
>> -{
>> -}
>> +static struct tst_test test = {
>> +	.test_all = verify_munlockall,
>> +};
>> -- 
>> 2.44.0
>>
>>
>> -- 
>> Mailing list info: https://lists.linux.it/listinfo/ltp
> 


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

      reply	other threads:[~2024-03-07  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  8:52 [LTP] [PATCH v3] munlockall: add test case that verifies memory has been unlocked Dennis Brendel
2024-03-06 10:24 ` Petr Vorel
2024-03-06 10:29 ` Li Wang
2024-03-06 10:41   ` Petr Vorel
     [not found]     ` <4d7c9726-d74f-41da-982c-91abca628649@redhat.com>
2024-03-06 12:44       ` Petr Vorel
2024-03-07  4:08         ` Li Wang
2024-03-06 15:26 ` Cyril Hrubis
2024-03-07  7:36   ` Dennis Brendel [this message]

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=71084990-17ef-461e-907e-e2bc39c2b236@redhat.com \
    --to=dbrendel@redhat.com \
    --cc=chrubis@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox