From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] waitpid01: Test all standard deadly signals
Date: Mon, 5 Feb 2024 18:34:52 +0100 [thread overview]
Message-ID: <20240205173452.GB218023@pevik> (raw)
In-Reply-To: <20240130162813.20278-1-mdoucha@suse.cz>
Hi Martin,
first this change (merged as ed5ccf6c1 ("waitpid01: Test all standard deadly
signals") is failing on 6.6 on Debian:
ed5ccf6c1 ("waitpid01: Test all standard deadly signals")
waitpid01.c:88: TINFO: Testing child: raise(sig)
waitpid01.c:109: TPASS: waitpid() returned correct pid 236064
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGIOT/SIGABRT
waitpid01.c:143: TPASS: Child dumped core as expected
waitpid01.c:109: TPASS: waitpid() returned correct pid 236071
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGALRM
waitpid01.c:109: TPASS: waitpid() returned correct pid 236072
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGBUS
waitpid01.c:143: TPASS: Child dumped core as expected
waitpid01.c:109: TPASS: waitpid() returned correct pid 236082
waitpid01.c:113: TFAIL: WIFSIGNALED() not set in status (exited with 0)
...
waitpid01.c:88: TINFO: Testing child: kill(getpid(), sig)
waitpid01.c:109: TPASS: waitpid() returned correct pid 236165
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGIOT/SIGABRT
waitpid01.c:143: TPASS: Child dumped core as expected
waitpid01.c:109: TPASS: waitpid() returned correct pid 236176
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGALRM
waitpid01.c:109: TPASS: waitpid() returned correct pid 236177
waitpid01.c:118: TPASS: WIFSIGNALED() set in status
waitpid01.c:126: TPASS: WTERMSIG() == SIGBUS
waitpid01.c:143: TPASS: Child dumped core as expected
waitpid01.c:109: TPASS: waitpid() returned correct pid 236187
waitpid01.c:113: TFAIL: WIFSIGNALED() not set in status (exited with 0)
...
But it works on 6.8.0-rc1-2.gf4ba5db-default Tumbleweed, which I tested it
before.
Also patch does not apply. I had to patch waitpid01 myself, hopefully I did that
correctly [1].
Kind regards,
Petr
[1] https://github.com/pevik/ltp/blob/mdoucha/waitpid05/testcases/kernel/syscalls/waitpid/waitpid01.c
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-02-05 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 16:28 [LTP] [PATCH] waitpid01: Test all standard deadly signals Martin Doucha
2024-01-30 17:22 ` Petr Vorel
2024-01-31 9:05 ` Martin Doucha
2024-01-31 10:14 ` Petr Vorel
2024-01-31 10:23 ` Martin Doucha
2024-01-31 16:13 ` Petr Vorel
2024-02-05 17:34 ` Petr Vorel [this message]
2024-02-05 18:13 ` Petr Vorel
2024-02-06 10:01 ` Martin Doucha
2024-02-06 10:44 ` Petr Vorel
2024-02-06 10:49 ` Martin Doucha
2024-02-06 11:00 ` 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=20240205173452.GB218023@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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 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.