From: blezhepekov <blezhepekov@suse.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] kernel/pty06: Skip test when TTY not available
Date: Tue, 05 Apr 2022 09:49:09 +0300 [thread overview]
Message-ID: <4adefcd96534fd7623cec275355c5063@suse.de> (raw)
In-Reply-To: <YitrrpkBJheQdUAa@yuki>
On 2022-03-11 17:33, Cyril Hrubis wrote:
> Hi!
>> Since TTYs under test are hardcoded, they
>> might not be available in some systems.
>
> Is the system you are running the tests on completely without ttys?
>
>> Signed-off-by: Bogdan Lezhepekov <blezhepekov@suse.de>
>> ---
>> testcases/kernel/pty/pty06.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/testcases/kernel/pty/pty06.c
>> b/testcases/kernel/pty/pty06.c
>> index b621f584f..250c38f6b 100644
>> --- a/testcases/kernel/pty/pty06.c
>> +++ b/testcases/kernel/pty/pty06.c
>> @@ -45,8 +45,6 @@ static struct tst_fzsync_pair fzp;
>>
>> static void *open_close(void *unused)
>> {
>> - sprintf(tty_path_b, "/dev/tty%d", test_tty_port);
>> -
>> while (tst_fzsync_run_b(&fzp)) {
>> tst_fzsync_start_race_b(&fzp);
>> int fd = SAFE_OPEN(tty_path_b, O_RDWR);
>> @@ -60,7 +58,6 @@ static void *open_close(void *unused)
>>
>> static void do_test(void)
>> {
>> - sprintf(tty_path_a, "/dev/tty%d", test_tty_port + 1);
>> int fd = SAFE_OPEN(tty_path_a, O_RDWR);
>>
>> tst_fzsync_pair_reset(&fzp, open_close);
>> @@ -80,6 +77,12 @@ static void do_test(void)
>>
>> static void setup(void)
>> {
>> + sprintf(tty_path_a, "/dev/tty%d", test_tty_port + 1);
>> + sprintf(tty_path_b, "/dev/tty%d", test_tty_port);
>> +
>> + if (access(tty_path_a, F_OK) != 0 || access(tty_path_b, F_OK) != 0)
>> + tst_brk(TCONF, "TTY(s) under test not available in system");
>
> There is no need for the != 0 could be simplified just to:
>
> if (access(...) || access(...))
> tst_brk(TCONF, ...);
>
>> tst_fzsync_pair_init(&fzp);
>> }
>>
>> --
>> 2.35.1
>>
>>
>> --
>> Mailing list info: https://lists.linux.it/listinfo/ltp
Hi Cyril,
Sorry for the delayed reply. I see the test requires an emulated
terminal (ttyX), whilst our system supports serial console only (ttySX).
What would be your recommendation, does it make sense to switch to
ttySX? I wasn't sure about it, so disabling seemed more logical.
Thanks,
Bogdan
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-04-05 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:39 [LTP] [PATCH v1] kernel/pty06: Skip test when TTY not available Bogdan Lezhepekov
2022-03-11 15:33 ` Cyril Hrubis
2022-04-05 6:49 ` blezhepekov [this message]
2022-04-11 11:25 ` Richard Palethorpe
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=4adefcd96534fd7623cec275355c5063@suse.de \
--to=blezhepekov@suse.de \
--cc=chrubis@suse.cz \
--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