From: pvorel <pvorel@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Delete fork09 test
Date: Tue, 19 Dec 2023 15:48:42 +0100 [thread overview]
Message-ID: <977d4dc47fa4c5163afc1a6646d4fb5a@suse.de> (raw)
In-Reply-To: <20231128125632.GB381183@pevik>
Hi all,
On 2023-11-28 13:56, Petr Vorel wrote:
> Hi Andrea,
>
>> From: Andrea Cervesato <andrea.cervesato@suse.com>
>
>> The fork09 test is actually testing what fork10 is already testing:
>> accessing an open child's file from parent. For this reason, we delete
>> it and let fork10 doing its job.
>
> in fork09 parent opens maximum number of files, child closes one and
> attempts to
> open another. That is not exactly the same, but it's very similar.
>
> I'm not sure if the scenario would really tests different code path in
> kernel/libc or not and we can happily delete it.
> Cyril, WDYT?
@Li, WDYT?
>
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-12-19 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 15:42 [LTP] [PATCH v1] Delete fork09 test Andrea Cervesato
2023-11-28 12:56 ` Petr Vorel
2023-12-19 14:48 ` pvorel [this message]
2023-12-20 10:40 ` Li Wang
2023-12-20 12:29 ` Petr Vorel
2024-03-12 15:19 ` Andrea Cervesato 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=977d4dc47fa4c5163afc1a6646d4fb5a@suse.de \
--to=pvorel@suse.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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