public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Filippo Storniolo <fstornio@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] syscalls/mlock05: add mlock test for locking and pre-faulting of memory
Date: Mon, 29 Apr 2024 15:48:21 +0200	[thread overview]
Message-ID: <Zi-lJZW244sciuW9@yuki> (raw)
In-Reply-To: <20240429133336.3166386-1-fstornio@redhat.com>

Hi!
> check VmRSS and VmLck variables from /proc/$pid/status.
> VmRSS size should at least as big as the memory allocation.
> VmLck size should be equal to the size of the memory allocation.

Now the test looks good, however I managed to make it fail. The test
fails if you run it with large enough -i paramater, for me running
'./mlock05 -i 10000' tend to produce failures at the end of the testrun:

tst_test.c:1741: TINFO: LTP version: 20240129-192-geca801321
tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s
mlock05.c:49: TPASS: Expect: (VmRSS=1048576) >= (MMAPLEN=1048576)
mlock05.c:52: TPASS: VmLck == MMAPLEN (1048576)
...
mlock05.c:52: TPASS: VmLck == MMAPLEN (1048576)
mlock05.c:49: TFAIL: Expect: (VmRSS=983040) >= (MMAPLEN=1048576)
mlock05.c:52: TPASS: VmLck == MMAPLEN (1048576)
mlock05.c:49: TFAIL: Expect: (VmRSS=983040) >= (MMAPLEN=1048576)
mlock05.c:52: TPASS: VmLck == MMAPLEN (1048576)

Summary:
passed   18332
failed   1668
broken   0
skipped  0
warnings 0
...

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2024-04-29 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 13:33 [LTP] [PATCH v2] syscalls/mlock05: add mlock test for locking and pre-faulting of memory Filippo Storniolo
2024-04-29 13:48 ` Cyril Hrubis [this message]
2024-05-02  9:12   ` Filippo Storniolo
2024-05-02 10:09     ` Cyril Hrubis

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=Zi-lJZW244sciuW9@yuki \
    --to=chrubis@suse.cz \
    --cc=fstornio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox