From: Li Wang via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: Luiz Capitulino <luizcap@redhat.com>
Subject: [LTP] [PATCH] hugeshmctl02: set 2 huge pages as an enforced requirement
Date: Thu, 30 Oct 2025 19:35:34 +0800 [thread overview]
Message-ID: <20251030113534.67798-1-liwang@redhat.com> (raw)
Set hugeshmctl02 to require exactly 2 HugeTLB pages and bail out
cleanly if unavailable. To prevent shmget EINVAL failures seen when
the environment cannot provide enough hugepages.
Stabilizes the test across constrained systems while keeping functional
intent intact.
=== error log ===
cmdline="hugeshmctl02 -s 1 -i 5;"
tst_hugepage.c:84: TINFO: 1 hugepage(s) reserved
tst_test.c:1709: TINFO: LTP version: 20240129
tst_test.c:1595: TINFO: Timeout per run is 0h 00m 30s
hugeshmctl02.c:105: TINFO: Testing variant: libc shmctl()
hugeshmctl02.c:119: TBROK: shmget #1: EINVAL (22)
Signed-off-by: Li Wang <liwang@redhat.com>
Cc: Luiz Capitulino <luizcap@redhat.com>
---
testcases/kernel/mem/hugetlb/hugeshmctl/hugeshmctl02.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testcases/kernel/mem/hugetlb/hugeshmctl/hugeshmctl02.c b/testcases/kernel/mem/hugetlb/hugeshmctl/hugeshmctl02.c
index d3f711129..82126f52c 100644
--- a/testcases/kernel/mem/hugetlb/hugeshmctl/hugeshmctl02.c
+++ b/testcases/kernel/mem/hugetlb/hugeshmctl/hugeshmctl02.c
@@ -143,5 +143,5 @@ static struct tst_test test = {
},
.setup = setup,
.cleanup = cleanup,
- .hugepages = {128, TST_REQUEST},
+ .hugepages = {2, TST_NEEDS},
};
--
2.51.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2025-10-30 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 11:35 Li Wang via ltp [this message]
2025-10-30 20:29 ` [LTP] [PATCH] hugeshmctl02: set 2 huge pages as an enforced requirement Petr Vorel
2025-10-31 2:27 ` Li Wang 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=20251030113534.67798-1-liwang@redhat.com \
--to=ltp@lists.linux.it \
--cc=liwang@redhat.com \
--cc=luizcap@redhat.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