From: Cyril Hrubis <chrubis@suse.cz>
To: spoorthy s <spoorthy@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] Hugetlb: Migrating libhugetlbfs shm-perms
Date: Wed, 11 Sep 2024 16:14:21 +0200 [thread overview]
Message-ID: <ZuGlvb1I_BXSOtpk@yuki.lan> (raw)
In-Reply-To: <3cfc8cf7-a7f4-4ccc-95d9-88bd358abd43@linux.ibm.com>
Hi!
> Test Description: Tests the behavior of shared memory when
> multiple threads attach to a segment with different permissions.
>
> At one point, reservation accounting of free hugepages between the parent
> and child processes may become inconsistent during memory operations.
> The parent creates 4 hugepages and a shared memory segment
> (size segment_size, permission 0640), attaches it, and initializes
> four parts with a pattern (0x55), then detaches it. Child processes
> are created in a loop, each reattaching the segment in read-only mode
> with SHM_RDONLY, detaching, and exiting. If attach/detach fails or
> if the reservation accounting of free hugepages doesn't match
> between parent and child, the test fails. If all child processes exit
> successfully and accounting matches, the test passes.
>
> Tested and verified the success of test case
>
> Signed-off-by: Spoorthy <spoorthy@linux.ibm.com>
Git complains that this patch is corrupted probably because the
"scissors" i.e. --- is missing after the Signed-off-by.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-11 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 10:41 [LTP] [PATCH v3] Hugetlb: Migrating libhugetlbfs shm-perms spoorthy s
2024-09-11 14:14 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-13 13:40 Spoorthy
2024-10-18 9:31 ` Li Wang
2024-11-06 9:44 ` Cyril Hrubis
2024-09-12 6:34 spoorthy s
2024-09-12 15:07 ` Cyril Hrubis
2024-09-11 10:31 spoorthy s
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=ZuGlvb1I_BXSOtpk@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=spoorthy@linux.ibm.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