From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Rewrite ns_exec tool using new LTP API
Date: Fri, 3 Mar 2023 15:38:20 +0100 [thread overview]
Message-ID: <ZAIGXHd3u1RMn5uZ@pevik> (raw)
In-Reply-To: <72ff2c7a-4054-6a5c-c801-0188af5a3edd@suse.com>
> Hi Petr,
> On 3/3/23 15:29, Petr Vorel wrote:
> > Hi Andrea,
> > Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > I'm going to merge without struct tst_test workarounds.
> > IMHO it works without it. Or am I missing something?
> Unfortunately it's needed because of SAFE_CLONE. We can't use it without
> forcing "forks_child = 1".
Yes, I read that in the comment. But the problem was somehow hidden.
It looks like Segmentation fault appear only if run on fresh reboot, that's why
I got confused it's not needed. Sorry for asking without looking into
safe_clone() before.
Also we had some discussion in the past whether tools should use the test
library at all (see below), but in this case I'd be for keeping it
(we don't want to reimplement tst_clone() and TST_RETRY_FUNC()).
> > Kind regards,
> > Petr
> Beware that this patch will touch the whole network testing suites since
> it's used in "tst_net.sh".
Yes, I know :). That was the reason why I also started to rewrite these tests,
with intention to move them to testcases/lib/ (although these files are both
tests and tools, we agreed with Cyril it's better to move them).
> Regards,
> Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-03 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 9:42 [LTP] [PATCH v1] Rewrite ns_exec tool using new LTP API Andrea Cervesato
2023-03-03 14:29 ` Petr Vorel
2023-03-03 14:21 ` Andrea Cervesato via ltp
2023-03-03 14:38 ` Petr Vorel [this message]
2023-03-03 15:08 ` Petr Vorel
2023-03-03 15:48 ` Petr Vorel
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=ZAIGXHd3u1RMn5uZ@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.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