From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Delete fork09 test
Date: Tue, 28 Nov 2023 13:56:32 +0100 [thread overview]
Message-ID: <20231128125632.GB381183@pevik> (raw)
In-Reply-To: <20231120154248.15048-1-andrea.cervesato@suse.de>
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?
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-11-28 12:56 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 [this message]
2023-12-19 14:48 ` pvorel
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=20231128125632.GB381183@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--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