From: Cyril Hrubis <chrubis@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/pipe08: Remove the test
Date: Tue, 25 Jul 2023 12:39:43 +0200 [thread overview]
Message-ID: <ZL-mb1nXfwpAklYr@yuki> (raw)
In-Reply-To: <20230719113906.22317-1-akumar@suse.de>
Hi!
> This test scenario of verifying SIGPIPE signal is being covered in
> syscalls/write05.c test.
Hmm, this one is actually hard to figure out. Indeed the write test
implmenents the SIGPIPE case, however it would make more sense to have
the SIGPIPE test in syscalls/pipe/ directory instead. I guess that any
kernel developer that would like to use LTP for testing changes in
pipe() implementation would rather want to have the test under pipe/
directory.
Maybe we should keep the pipe08 test and remove the case from the
write05 test instead? Or should we keep both?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-07-25 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 11:37 [LTP] [PATCH] syscalls/pipe08: Remove the test Avinesh Kumar
2023-07-21 9:32 ` Petr Vorel
2023-07-25 10:39 ` Cyril Hrubis [this message]
2023-08-02 9:25 ` Avinesh Kumar
2023-08-02 10:00 ` Cyril Hrubis
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=ZL-mb1nXfwpAklYr@yuki \
--to=chrubis@suse.cz \
--cc=akumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.