From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission
Date: Tue, 5 May 2020 17:11:23 +0200 [thread overview]
Message-ID: <20200505151123.GA9949@dell5510> (raw)
In-Reply-To: <87d07isaka.fsf@our.domain.is.not.set>
Hi Richard,
> This looks similar to the issue reported by Jan:
> https://github.com/linux-test-project/ltp/issues/674
> Is this the full output?
Here it is:
# ./pty04
tst_test.c:1244: INFO: Timeout per run is 0h 05m 00s
pty04.c:127: INFO: PTS path is /dev/pts/29
pty04.c:202: INFO: Netdev is sl0
pty04.c:211: INFO: Netdev MTU is 8192 (we set 8192)
pty04.c:228: INFO: Bound netdev 51 to socket 5
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:301: INFO: Reading from socket 5
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:176: PASS: Wrote PTY 1
pty04.c:186: PASS: Wrote PTY 2
pty04.c:305: PASS: Read netdev 1
pty04.c:309: PASS: Read netdev 2
pty04.c:315: PASS: Reading data from netdev interrupted by hangup
pty04.c:342: INFO: Sent hangup ioctl to PTS
pty04.c:191: PASS: Writing to PTY interrupted by hangup
pty04.c:344: INFO: Sent hangup ioctl to PTM
pty04.c:127: INFO: PTS path is /dev/pts/32
pty04.c:202: INFO: Netdev is slcan0
pty04.c:211: INFO: Netdev MTU is 16 (we set 16)
pty04.c:228: INFO: Bound netdev 52 to socket 8
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:301: INFO: Reading from socket 8
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:176: PASS: Wrote PTY 1
pty04.c:186: PASS: Wrote PTY 2
pty04.c:305: PASS: Read netdev 1
pty04.c:309: PASS: Read netdev 2
pty04.c:315: PASS: Reading data from netdev interrupted by hangup
pty04.c:342: INFO: Sent hangup ioctl to PTS
pty04.c:191: PASS: Writing to PTY interrupted by hangup
pty04.c:344: INFO: Sent hangup ioctl to PTM
Summary:
passed 12
failed 0
skipped 0
warnings 0
# ./pty04
tst_test.c:1244: INFO: Timeout per run is 0h 05m 00s
pty04.c:127: INFO: PTS path is /dev/pts/29
pty04.c:202: INFO: Netdev is sl0
pty04.c:211: INFO: Netdev MTU is 8192 (we set 8192)
pty04.c:228: INFO: Bound netdev 53 to socket 5
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:301: INFO: Reading from socket 5
tst_buffers.c:55: INFO: Test is using guarded buffers
pty04.c:176: PASS: Wrote PTY 1
pty04.c:186: PASS: Wrote PTY 2
pty04.c:305: PASS: Read netdev 1
# BLOCKS
tst_checkpoint.c:147: BROK: pty04.c:340: tst_checkpoint_wait(0, 10000): ETIMEDOUT (110)
tst_test.c:373: BROK: Reported by child (10018)
safe_macros.c:258: BROK: pty04.c:307: read(5,0x7f3920c4a001,8191) failed, returned -1: ENETDOWN (100)
pty04.c:191: PASS: Writing to PTY interrupted by hangup
tst_test.c:373: WARN: Reported by child (10016)
Summary:
passed 4
failed 0
skipped 0
warnings 1
It looked like it regularly changes working and failing, but sometimes it fails
several times. Also sometimes it works when -i2 (but mostly fails).
Kind regards,
Petr
next prev parent reply other threads:[~2020-05-05 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:16 [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission Richard Palethorpe
2020-05-05 10:16 ` [LTP] [PATCH v4 2/2] pty04: Add SLCAN ldisc and check for CVE-2020-11494 Richard Palethorpe
2020-05-05 13:35 ` Cyril Hrubis
2020-05-05 13:55 ` Petr Vorel
2020-05-05 15:18 ` Richard Palethorpe
2020-05-05 15:27 ` Petr Vorel
2020-05-05 13:37 ` [LTP] [PATCH v4 1/2] pty04: Use guarded buffers for transmission Petr Vorel
2020-05-05 14:47 ` Richard Palethorpe
2020-05-05 15:01 ` Petr Vorel
2020-05-05 15:11 ` Petr Vorel [this message]
2020-05-06 8:47 ` Richard Palethorpe
2020-05-06 10:49 ` Jan Stancek
2020-05-06 10:56 ` Li Wang
2020-05-06 11:14 ` Jan Stancek
2020-05-06 11:38 ` Petr Vorel
2020-05-06 12:06 ` Jan Stancek
2020-05-06 12:17 ` Petr Vorel
2020-05-06 12:20 ` Jan Stancek
2020-05-06 12:49 ` Cyril Hrubis
2020-05-06 13:49 ` 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=20200505151123.GA9949@dell5510 \
--to=pvorel@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 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.