From: xuyang2018.jy@fujitsu.com <xuyang2018.jy@fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] shmget03: fix test when some shm segments already exist
Date: Mon, 12 Jul 2021 02:31:52 +0000 [thread overview]
Message-ID: <60EBA9C3.4050103@fujitsu.com> (raw)
In-Reply-To: <YObpRzTjx8T2GAZn@yuki>
Hi All
> Hi!
>>>> Yes, good point, that would be more precise for ENOSPC testing.
>>> AFAIK, ltp doesn't support parallel test now. I think parallel test
>>> maybe a future plan that is why we use docparase to collect each case's
>>> used resources(so we can convert many groups, like pid, memory, disk
>>> space..., then we can run pid group and memory groups test case parallelly).
>> Yes, parallel support is not supported atm. Richie and Cyril has done some work
>> on runltp-ng to support it. Yes, first it's needed to add support in resources
>> (docparse), see Cyril's old block post [1].
>
> Besides most of the SHM tests will crash and burn if executed in
> parallel. The SysV IPC shares a global namespace and because of that we
> can't really write tests without assuming that we are the only one
> manipulating them when the test is executed.
I guess we should reach a consensus that how to fix this problem
1)use for loop to trigger this error
2)use CLONE_NEWIPC to trigger this error
3)Or we are the only one that use shm and we can add a api to count the
existed_cnt
ps: I don't want to leave this problem too long time.
Best Regards
Yang Xu
>
next prev parent reply other threads:[~2021-07-12 2:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 10:57 [LTP] [PATCH] shmget03: fix test when some shm segments already exist Alexey Kodanev
2021-07-06 12:49 ` Li Wang
2021-07-06 13:43 ` Alexey Kodanev
2021-07-06 14:18 ` Alexey Kodanev
2021-07-07 1:26 ` Li Wang
2021-07-07 1:59 ` xuyang2018.jy
2021-07-07 14:12 ` Alexey Kodanev
2021-07-08 11:02 ` Petr Vorel
2021-07-08 12:02 ` Cyril Hrubis
2021-07-12 2:31 ` xuyang2018.jy [this message]
2021-07-12 7:46 ` Alexey Kodanev
2021-07-12 8:41 ` Petr Vorel
2021-07-12 8:46 ` Alexey Kodanev
2021-07-14 9:33 ` Cyril Hrubis
2021-07-14 10:00 ` Petr Vorel
2021-07-14 10:17 ` xuyang2018.jy
2021-07-07 1:50 ` xuyang2018.jy
2021-07-07 2:21 ` Li Wang
2021-07-07 4:30 ` xuyang2018.jy
2021-07-08 2:24 ` xuyang2018.jy
2021-07-08 8:27 ` Li Wang
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=60EBA9C3.4050103@fujitsu.com \
--to=xuyang2018.jy@fujitsu.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