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: Wed, 14 Jul 2021 10:17:04 +0000 [thread overview]
Message-ID: <60EEB9CF.7040001@fujitsu.com> (raw)
In-Reply-To: <YO61swgamAEnoAFj@pevik>
Hi Cyril, Petr
> Hi,
>
> ...
>> We will need to have some kind of flag that would tell the testrunner
>> that the test is using/modifying SysV IPC anyways as without namespaces
>> these tests cannot run in parallel at all.
>
>> So I would say that we should:
>
>> * Write these tests in a way that they expect that they are the only
>> process that modifies these resources during the testrun
>
>> * Mark all these tests with .sysv_ipc flag in the tst_test structure
>
>> * Then we can easily add support for running them in a separate
>> namespace in the test library
>
>> Does that sound reasonable?
> +1
+1
Since now ltp test libary uses fork_testrun, I wonder whether we should
add clone_testrun. So test's setup/test/cleanup function are all in new
namespace.
Maybe we should support two ways for running test cases in
lib/tst_test(fork and clone)?
And we can add clone and flag argument(the value can be
CLONE_NEWIPC/CLONE_NEWNET/CLONENEWPID or more ) in tst_test struct.
ps: Just a initial idea
Best Regards
Yang Xu
> Kind regards,
> Petr
next prev parent reply other threads:[~2021-07-14 10:17 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
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 [this message]
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=60EEB9CF.7040001@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